Hello,
I'm developing huge SSIS-packages which often have to perform SQL Tasks running lot of plain sql statements. For developing the sql statements I'm using SQL Server Data Tools which supports debugging, syntax highlighting and IntelliSense (which isn't supported in SSIS with SQL Tasks). This is very important because the sql files can be very huge. Later I copy the resulting sql statements in the SQL Task of the SSIS-package. The deployment to SQL Server 2012 will be performed during Visual Studio.
I'm searching for a solution to reference SQL files in a SQL Task. I know method for flat file connections or direct connections in SQL Task. This is possible but therefore I need a directory on our SQL Server where the productive SQL files are stored (path can be configured over parameter and variables, thats OK) and the development will always be on the productive system (if I don't want to copy the statements of the SQL files).
Best solution will be in my opinion to reference SQL files with relative paths. At build time the sql files should be packed to the resulting ispac file. During deployment with the wizard (or in Visual Studio) the sql files should be eather stored on file system (predefined directory) or in SSISDB database. As result I've got a fully ipsac solution packed in a single which contains all parts and can be easy transfered an stored. The development of my SQL statements and the SSIS packages can be made with one tool, the SSDT. Versioning can be made with Team Foundation Server because all parts are in one VS solution. But this functionallity doesn't exist at SSDT or MS SQL Server 2012.
The folder structure of a SSIS project contains a folder "Miscellaneous". I've tried to store sql file in it. But opening for editing will result in a crash (and restarting) of Visual Studio (using Visual Studio 2010 Ulitmate with SP1 and installed
Microsoft SQL Server Data Tools). This must be a bug or not? At the moment only possibility for me is to add another project (like C#) to the VS solution which contains the sql files. Then performing, debugging and editing of sql files is possible and I'm
only using one IDE and one solution for develope sql statements and SSIS.
Does any body have a solution for this scenario? Why doesn't Microsoft implement such a functionality? How can I expand functionality of ipsac files for storing other files (like sql, txt or so on)? Is it possible to run sql statements stored in SSISDB tables in SSIS?