|
I've got a new development machine that I'm configuring. I want to put both SQL Server and Visual Studio 2008 onto this box. It's running Windows 7, so I'll put the developer edition onto it. I'd been wondering if the order in which I install Visual Studio (VS) and SQL Server makes a difference, and it doesn't look as though it does. But one person suggested that I install VS first, but not install SQL Server 2005 Express, which normally goes on when you install VS. I've been thinking of putting SQL Server 2008 Developer Edition on (I have no experience with it, but do with SQL 2005, and now would be a good time to give the new version of SQL Server a try.) However, I'm wondering if there's some good reason why I should not install SQL Express, if I want to put on SQL Server 2008?
(comments are locked)
|
|
Generally I would have installed SQL Server 2008 first, then either VS or 2005 Express. Once you get the base established with 2008, the other installs don't seem to cause issues.
(comments are locked)
|
|
I have heard some anecdotal evidence where installing Express with VS does then cause issues later on if you want to install dev edition, but never actually experienced it.
(comments are locked)
|
|
Ha funny you should say that - I am at this very moment installing 2K8 on a fresh Windows 7 install... For 2005 you need Service Pack 3, and for 2008 you need Service Pack 1 - so get downloading those if you haven't already. I skipped the 2005 express that VS2008 wanted to install, and just went with developer editions of both SQL Server 2005 and 2008. The good reason to not install SQL Express is that if you have access to developer edition, then there's no reason to install it. I have some ASP.NET apps I wrote, that use SQL 2005 Express. If I don't install SQL Express, then would I be able to use these ASP.NET apps with SQL 2008 Developer edition?
Oct 21 '09 at 02:06 PM
Rod
There is nothing in Express that isn't in Developer, because Developer is functionally equivalent to Enterprise Edition, just not licensed for production use. So - yes you will be able to use your ASP.NET apps for development / testing, but you would not be able to use Developer edition to do the database serving on an actual web site.
Oct 21 '09 at 04:03 PM
Matt Whitfield ♦♦
That's fine, thanks Matt.
Oct 21 '09 at 05:52 PM
Rod
I'm now having some difficulty running VS 2008 Pro, with the ASP.NET AJAX library, that is related to not having SQL Express installed. At least indirectly. I'm getting error messages that say, "The application attempted to perform an operation not allowed by the security policy." To fix this I've gone into the project's ASP.NET Configuration and tried changing security there. However, I was blocked because it couldn't access SQL Server Express, because I intentionally left it out when I installed SQL Server 2008, which is what I thought I was supposed to do.
Oct 31 '09 at 12:17 PM
Rod
(comments are locked)
|
|
There is no significant reason that it matters, but do be careful with the defaults. By default the first instance of SQL Server you install is the primary one and all others are named. You can of course change that and name the first instance and force a later one to be primary, but it is generally simpler just to install the one you want to be the primary instance first.
(comments are locked)
|
