SSIS Development Workflow
-
I'm currently involved in migrating a few SQL apps that currently use DTS to SQL 2008 R2, and I'm looking at the SSIS development workflow. Is it correct that you can *only* develop SSIS packages on a machine with a full version of SQL Server installed (i.e. not Express)? I've got the VS2008 BIDS installed, but if I try to create an IS project it complains that I don't have Standard, Ent, Dev or Eval versions of SQL installed. Do people generally install these full SQL Server editions on their dev workstations, then deploy to the dev/test/prod servers? Or do they use Remote Desktop? (Which seems a really clunky way tbh!) What about the VS2010 SQL Data Tools? Do they overcome this limitation? (I would try but we're still on XP-SP3. DTS seemed much easier, Enterprise Manager could develop packadges on whatever server it could connect to, or you could develop local files.
-
I'm currently involved in migrating a few SQL apps that currently use DTS to SQL 2008 R2, and I'm looking at the SSIS development workflow. Is it correct that you can *only* develop SSIS packages on a machine with a full version of SQL Server installed (i.e. not Express)? I've got the VS2008 BIDS installed, but if I try to create an IS project it complains that I don't have Standard, Ent, Dev or Eval versions of SQL installed. Do people generally install these full SQL Server editions on their dev workstations, then deploy to the dev/test/prod servers? Or do they use Remote Desktop? (Which seems a really clunky way tbh!) What about the VS2010 SQL Data Tools? Do they overcome this limitation? (I would try but we're still on XP-SP3. DTS seemed much easier, Enterprise Manager could develop packadges on whatever server it could connect to, or you could develop local files.
cjb110 wrote:
*only* develop SSIS packages on a machine with a full version of SQL Server
That was my experience when I started using it two months ago.
-
I'm currently involved in migrating a few SQL apps that currently use DTS to SQL 2008 R2, and I'm looking at the SSIS development workflow. Is it correct that you can *only* develop SSIS packages on a machine with a full version of SQL Server installed (i.e. not Express)? I've got the VS2008 BIDS installed, but if I try to create an IS project it complains that I don't have Standard, Ent, Dev or Eval versions of SQL installed. Do people generally install these full SQL Server editions on their dev workstations, then deploy to the dev/test/prod servers? Or do they use Remote Desktop? (Which seems a really clunky way tbh!) What about the VS2010 SQL Data Tools? Do they overcome this limitation? (I would try but we're still on XP-SP3. DTS seemed much easier, Enterprise Manager could develop packadges on whatever server it could connect to, or you could develop local files.
The devs on our team doing SSIS do not have the SQL Server database installed, they use SSMS (I'd need to confirm this on Monday).
Never underestimate the power of human stupidity RAH
-
The devs on our team doing SSIS do not have the SQL Server database installed, they use SSMS (I'd need to confirm this on Monday).
Never underestimate the power of human stupidity RAH