![]() Ran dtinstall.exe to install the packages on the server. They compile and execute correctly from within VS.Įach package has 3 Configuration Files (for test, preview and production scenarios).Ĭonfigured the 2 Packages' TargetServerVersion to "SQL Server 2016", due to a compatibility issue discovered upon installing the Deployment Utility.Ĭreated the Deployment Utility using the Legacy Package Deployment Model.Ĭopied the Deployment Utility files from the C.\Deployment folder to a folder on the F: drive on the server. The two Visual Studio 2019 packages were developed in the C: drive on the server. The dtexecui.exe is found ONLY in the following Folder: We just installed SSIS from the SQL Server Setup, realizing we were missing that component.Īs a result of all these installations, dtinstall.exe & dtexec.exe are in the following folders:Ĭ:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\SSIS\140\BinnĬ:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\CommonExtensions\Microsoft\SSIS\150\BinnĮ:\Program Files\Microsoft SQL Server\130\DTS\BinnĮ:\Program Files (x86)\Microsoft SQL Server\130\DTS\BinnĮ:\Program Files (x86)\Microsoft SQL Server\120\DTS\BinnĮ:\Program Files (x86)\Microsoft SQL Server\110\DTS\BinnĮ:\Program Files (x86)\Microsoft SQL Server Management Studio 18\Common7\IDE\CommonExtensions\Microsoft\SSIS\150\Binn ![]() We recently installed Visual Studio 2019 on the db server due to problems with file access when running VS2019 locally and using a VPN to access the network. We installed Visual Studio 2017 in January but didn't use it at that time. The database data files are on the E: drive. We installed SQL Server 2016 STANDARD EDITION in January. ![]() A component of that system was an SSIS project created with VS2005. We are moving an existing system from a SQL Server 2005 system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |