IBlog<Johan>

This and that in a developer's life in general

News

Follow johandanforth on Twitter

Random Links

Walkthroughs and Tutorials

Installing SQL 2005 Express on top of SQL 2000

I'm going to install the VS 2005 beta on one of my lab boxes here, and this machine already has SQL 2000 on it. What happens if I check to install SQL 2005 Express during the VS 2005 installation? Will it upgrade 2000 to 2005 or what?

I'm sure people has tried this out there, but if I don't get any response I'll just go ahead and try and see what happens :)

EDIT 1: Brilliant... Ok, first I installed VS 2005 and all the MSDN stuff, then I rebooted the machine and tried to add SQL 2005 Express. Problem is that it hung in the end (progress meter near 100%) and refused to finish. So I killed the setup process and had a look at the box. It looks like SQL 2005 was installed properly and everything. Just one thing I wonder now... and this sounds stupid maybe, but how do I know which database service I'm running against?? *confused*

EDIT 2: Ok, I'm almost there! I downloaded the SQL Server Express Books Online and I'm following the walkthrough to create a database app. To be cont.

EDIT 3: Right, I'm in! It was very easy once I got into it (as usual). 1) Install SQLExpress 2) Make sure SQLExpress service is started and you may also want to start the SQL Browser service and enable some of the other network protocols if you're not running locally only 3) Use your favourite SQL manager (like the server browser in VS 2005) and access the database instance by calling it .\SQLExpress or <computername>\SQLExpress.

*running off to try some of the new features*

Posted: Aug 11 2004, 08:30 AM by jdanforth | with 10 comment(s)

Comments

William Luu said:

Hi Johan, I've got SQL Server 2000 as well as SQL Server 2005 Express installed on my computer with no problems at all.

So you should be fine! :)

You can use both at the same time if you like... They live in two different processes!

# August 11, 2004 2:39 AM

Thomas Flindt Lynge said:

As Johan, I have had no problems running SQL 2000 and 2005 on the same computer, BUT uninstalling SQL 2005 Express will delete some core files with the result that you can not use the Enterprise Manager for SQL 2000 anymore. Reinstalling SQL 2000 is not an option either. You have to uninstall the .NET framework first.
# August 11, 2004 2:52 AM

Johan Danforth said:

Ok, thanks for the info. I'll download the latest SQL 2005 Express beta 2 from http://www.microsoft.com/downloads/details.aspx?FamilyId=62B348BB-0458-4203-BB03-8BE49E16E6CD&displaylang=en and see if it installs properly.
# August 11, 2004 4:00 AM

Hector Correa said:

Here are my notes on things that I found when using SQL 2005 Express for the first time. Hope they help you.

http://www.hectorcorrea.com/DotWiki.htm?topic=UsingSqlExpress
# August 11, 2004 8:30 AM

Mark Heimonen said:

I have VS 2003, VS 2005 beta, SQL Server 2005 Express, and SQL Server 2000 all running on the same machine without a problem. I have no problems using Enterprisse Manager for SQL Server 2000

The only issue I faced was getting my VS 2003 ASP.NET Applications working again after installing VS 2005 and SQL Server 2005. After running aspnet_regiis -r, and setting the application directory to use the 1.1 framework through IIS, I was back in business.

-Mark
# August 11, 2004 11:52 AM

Mark Heimonen said:

I guess I spoke too soon....I now get an error ("Error 195: 'schema_name' is not a recognized function name"), if I attempt to "Manage Triggers" in Sql Server 2000/Enterprise Manager.

Rather silly of me to attempt installing the beta products on my primary development laptop. Trigger management is about the only task I don't normally do through query analyzer, so I guess it's time for me do digging through BOL.

So, if I uninstall SQL Server 2005/VS 2005 Express, and then re-install SQL Server 2000, will Enterprise Manager function correctly again?
# August 11, 2004 2:26 PM

Mark Heimonen said:

According to http://blogs.msdn.com/sqlexpress/archive/2004/07/04/172956.aspx, the problem with Enterprise Manager can be fixed by re-registering the version of SQLDMO used by SQL Server 2000.

I'm not exactly sure what this means. Can anybody point me in the right direction? I found this article:

http://support.microsoft.com/?id=326613

which shows how to create a vs project to install QL Distributed Management Objects (SQL-DMO) for Microsoft SQL Server 2000. Is this a safe procedure to follow? I'm more concerned about making sure my existing VS2003/SQL 2000 projects than anything else.
# August 11, 2004 2:41 PM

Mark Heimonen said:

Last post...
I should've read my first link a little closer. To fix the bugs with EM, You just need to navigate to the install directory Microsoft SQL Server\80\Tools\Binn directory and run "regsvr32 sqldmo.dll".

*Note that doing this will cause EM to not work with SQL Server 2005 Express.
# August 11, 2004 2:54 PM

Johan Danforth said:

Cool, thanks for all the info Mark. If I stumble into any strange stuff, I'll post it here.
# August 11, 2004 5:25 PM

Mark Heimonen said:

Update....

I'm not really sure if it's related to installing the other products, but I ended up experiencing some weird bugs on my system the past few days. I outlined some of the details here:
http://forums.aspfree.com/t35176/s.html

In addition to the problem I mentioned in that post, I also started seeing the error while using query analyzer to access a database hosted on another computer.

I have been unable to correct the issue, and have now given up. I'm currently reinstalling the OS on my laptop.

Again, I don't know if the issues are at all related. As far as I can remember, the problems didn't turn up until after I tried installing Oracle.
# August 19, 2004 6:18 PM