CODEWITHSUNDEEP
visual-studio-2010compatibilitysql-server-2008-r2
Raven Dreamer
Raven Dreamer

Reputation: 7140

Does SQL Server 2008 R2 play nice with VS2010?

I know from firsthand experience that if you wanted to install both SQL Server 2008 and Visual Studio 2008 on the same machine, you had to jump through all sorts of service packs and installation orders to ensure that both programs ran properly.

In my case, I have VS 2010 installed on my PC currently, and find I'm in need of the SQL Enterprise Manager, which is not included from the Visual Studio installation. What, if anything, do I need to do before installing SQL Server 2008 R2?

Related question: Does it matter which sub-version of SQL Server I install? (Thanks to my University connection, I have my pick between Developer, Enterprise, Standard, and Web; is one preferred in my case?)

Upvotes: 0

Views: 2814

Answers (2)

user166390
user166390

Reputation:

The "connect to DB" works well in VS2010 and 2008R8 works well enough with LINQ (as well as LINQ works, anyway). I would recommend using SQL Server Management Studio to actually deal with SQL Server though.

However, BIDS does not work in VS2010. VS2008 is needed for it (or perhaps VS2005? I know not). I have VS2010 and VS2008 both installed for this reason.

The order of installation does not matter as long as none of the installations are "mysteriously corrupt" (of course VS2008 is a requirement for BIDS, but that's not a core part of SQL Server). Yes, you need to install the latest service packs for VS2008, but that should be done anyway. No "hoops". Just possibly an annoying SQL Server installation restart.

As far as sub-version: depends on what you need. MSDN should cover the differences in features fairly well. One thing to consider is avoiding a lock-in of more expensive version for features used (that aren't needed). It may or may not make a difference, depending upon target audience.

Upvotes: 4

kenwarner
kenwarner

Reputation: 29120

Install SQL Server before Visual Studio 2010, if for no reason other than avoiding accidentally installing SQL Server Express during the VS installer. I'd also recommend using the Developer edition of SQL Server since that's what it's designed for

Upvotes: 0

Related Questions