September 8, 2010 at 8:04 am
So I've been happily developing SSIS packages in VS 2005. But recently had SQL 2008 R2 installed on my machine (for upcoming projects). Now I can't open any script tasks. When I click the "Design Script" button nothing happens. I don't even see a process start in task manager.
The research I've done indicates that this has something to do with SP2. The only difference is, the posts I've seen say that they get an error message and/or they see orphan processes (vsenv.exe, as I recall). I get nothing. Anybody else encounter this?
I also have VS 2008 Pro installed on this machine and I tried upgrading the packages but they failed on the script task. Which goes back to my previous problem. Again, anyone have this problem?
I looked into building new projects in VS 2008 but, as I'm sure you all know, there's no SSIS project type in 2008. So how would SSIS package work in 2008? There seem to be people doing it, but I don't see how. Would I use a SQL Server project type? I don't see any way to manipulate the contents of a package; no control flow page, no way to get to tasks, etc. There are SQL Script Task and Component projects, but I need a little more than that...
I think the best solution is to go back to an earlier image of the machine prior to the SQL 2008 R2 install. I suspect that simply uninstalling it will leave crap behind and just cause more headaches. Thoughts?
Also, other parts of the team are starting to use VS 2010 and I'm fully aware there is absolutely no support for SSIS there. According to MSFT, that won't happen until the "next release of SQL Server".
So, it looks like we're going to have one machine with VS and SQL 2005 (existing databases will remain on 2005 servers, new ones going to 2008 R2) and another machine with VS 2010 and SQL 2008 R2. Pain in the neck, but what can you do?
If anyone has had similar experiences and can offer any insight, it would be greatly appreciated!
Thanks
September 8, 2010 at 8:52 am
I did figure out how to convert the project and packages to VS 2008; go to the SQL Server 2008 R2 program group and click the Business Development Studio item. Brings up VS with different features...
September 8, 2010 at 9:05 am
Thanks for the update. My guess is that the R2 versions of SSIS aren't compatible with VS 2005
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
September 8, 2010 at 9:55 am
FYI, the break in SSIS package compatibility happened with SQL 2008. SQL 2005 packages must be upgrade for 2008; 2008 packages are not backwards compatible with 2005. SQL 2008 and 2008 R2 packages are compatible with each other.
In order add the ability to handle SSAS, SSIS, and SSRS, projects with Visual Studio, you need to do a SQL Server (2008 or 2008R2 in this case) install on the development machine. The only option you should need to install is the Developer Tools. Which version of SQL server you install determine which version of packages you can open/develop.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 8, 2010 at 10:14 am
Thank you both for your responses, much appreciated!
One question that arose in a meeting I just got out of was whether VS 2010 has support for SSIS. From what I've found so far, MSFT says it does not, until the "next release" of SQL. I don't believe 2008 R2 is that next release but another developer here believes that it is. Can anyone offer any insight on this issue?
Thanks again!
September 8, 2010 at 10:29 am
kdbarrett (9/8/2010)
Thank you both for your responses, much appreciated!One question that arose in a meeting I just got out of was whether VS 2010 has support for SSIS. From what I've found so far, MSFT says it does not, until the "next release" of SQL. I don't believe 2008 R2 is that next release but another developer here believes that it is. Can anyone offer any insight on this issue?
Thanks again!
Can you elaborate on what you mean by support for SSIS?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 8, 2010 at 1:02 pm
Being able to create, edit, run, etc., SSIS packages in VS 2010.
September 8, 2010 at 1:13 pm
kdbarrett (9/8/2010)
Being able to create, edit, run, etc., SSIS packages in VS 2010.
I don't know what MS has planned for that, but the way is works now, you install that functionality from the SQL Server DVD.
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 8, 2010 at 1:22 pm
Right, SQL Server 2008 R2, which runs VS 2008 with different options than "regular" VS 2008. So you can open SSIS projects, work on packages, etc., with VS 2008, but not with VS 2010. At least, that's my understanding.
September 8, 2010 at 1:25 pm
kdbarrett (9/8/2010)
Right, SQL Server 2008 R2, which runs VS 2008 with different options than "regular" VS 2008. So you can open SSIS projects, work on packages, etc., with VS 2008, but not with VS 2010. At least, that's my understanding.
Why do you need it with VS 2010? It will be available as BIDS for each version of SQL Server you install. Isn't that enough?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
September 8, 2010 at 2:16 pm
A manager was looking to standardize development environments (prompted by the problem I was having, which started this post). One group needs VS 2010 for what they're doing. If it was possible to use VS 2010 for what I'm doing, we would all get 2010. It will probably still get installed, I just won't be using it.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply