My home machine has sql 2005 and Visual Studio 2005 installed. I uninstalled VS 2005 (RTM)and installed VS 2008 (RTM) in its place. I then found that the SSIS templates were missing. Lesson: don't uninstall VS 2005 if you want to use SSIS 2005! 1. Is there any "workaround" to this issue? 2. (If the answer to 1 is "No")I willinstall VS 2008 side-by-side with VS 2005 on the same box. When the SSIS issue is finally resolved, can I uninstall VS 2005 without doing damage to theVS 2008 install? TIA, Barkingdog

SSIS 2005 packages can only be created and edited with VS 2005. There is no plan to ever support editing SSIS 2005 packages with VS 2008, so this is not an "issue" that will be "resolved." You can, however, safely run SSIS 2005/VS 2005 side-by-side with VS 2008.

>>> There is no plan to ever support editing SSIS 2005 packages with VS 2008, So will VS 2008 provideits own "SSIS" project template versions or are they taking a totally different approach? Barkingdog

SQL Server 2008 uses the VS 2008 environment to host BI project templates. If you download CTP6, it's already present.

barkingdog wrote: >>> There is no plan to ever support editing SSIS 2005 packages with VS 2008, So will VS 2008 provideits own "SSIS" project template versions or are they taking a totally different approach? Barkingdog Just as SQL Server 2005 uses Visual Studio 2005 for its SSIS development environment, SQL Server 2008 uses Visual Studio 2008 for its SSIS development environment. The approaches are the same; the versions are different.

Just to make sure I understand what you're saying here:In VS 2008 you can develop SQL 2000 Database Projects, SQL 2005 Database projects, and .NET 2.0 projects and solutions. In almost every way, VS 2008 touts itself as a superset of VS 2005, rendering VS 2005 obsolete. You can even connect seamlessly with TFS 2005 using VS 2008. But you can't do any business intelligence projects on SQL 2005 using VS 2008? I certainly hope they reconsider.

But you can't edit SS/BIDS 2K5 solutions with VS2K8 (the subject of the thread); wouldn't call that a superset It's the same deal with SSRS 2K5; the RDL schema is different in SSRS 2K8, and there's no upgrade path for that either (although my MS sources tell me they're working on 1). Wonder what the deal is with SSAS solutions; they probably changed all theBI solution/project/report (anything 2K5) formats in 2K8. JPD (Just Plain Dumb); here we are trying to fight coupling and they've gone and coupled the database and development environments!

FYI, same deal for SSAS. I guess since offering the ability to do these projects in a VS/sharing VS components, they had to go down this path. I guess we traded db/dev env independence for the powere/flexibility/familiarity of being able to use a VS derivative (BIDS) to manipulate these solutions.

Yeah, the decision to make SSIS packages for 2005 uneditable from VS 2008 was a terrible decision. MS should have at least made this very clear when releasing VS 2008. How many people want to support multiple development environments? None. At least VS 2008 should be able to work with 2005 SSIS packages. Also, what do you think the chances are that developers will risk using any new MS technologies when the upgrade path between versions is not there. Once again, the answer is none. Now, not only are we not likely to upgrade to SQL Server 2008, because there is no migration path for 2005 SSIS packages, we're definitely going to wait several years before ever attempting a move to a new version of the development environment.

bpeikes wrote: Now, not only are we not likely to upgrade to SQL Server 2008, because there is no migration path for 2005 SSIS packages, we're definitely going to wait several years before ever attempting a move to a new version of the development environment. Perhaps you misunderstood the earlier messages - you can migrate 2005 packages to 2008. You simply open them in VS2008, it will prompt you to upgrade, and they will be converted to SQL Server 2008 packages. Works very well, too - I haven't encountered any issues with it.

Right, but they don't run on SQL 2005.

I agree, this sucks! I went to great lengths to uninstall VS2005 and now I can't edit my SSIS projects. I'm going to attempt to find an open source solution so this won't happen again. What a hassle.

Just as a note, one of the reasons we're not upgrading our servers to SQL Server 2008, is because even though we bought two licenses of Enterprise 2005 and 2 licenses for Standard 2005 SQL Server, the cost to upgrade to 2008 only a year later is only slightly cheaper than our original licenses. It makes no sense.

bpeikes wrote: Right, but they don't run on SQL 2005. The Merge statement doesn't work on 2005 either. It's fairly common that new functionality (or enhanced features) require the new servers. I can't run a 2008 SSRS report on a 2005 SSRS report server, nor can I run an app that uses Oracle 10G specific functionality against an Oracle 8i server.

I guess folks who've bought VS2008 to develop apps to target SQL 2005 won't be very happy then !!

You can always ask for a 'downgrade'

Yeah, this is why Microsoft is no longer seen as relevant and foward thinking.