I would like to upgrade3 my development machine to Windows 7.
I moved all my development tools without real problems. Only SQL Server 2000
is not working. And I've read many comments saying that it is not supported.
So, I can install SQL Server 2008 on my development machine and connect to
the existing (on production servers) databases.
But what do I do with the existing SQL 2000 databases running now on my
Windows XP development machine? If I attach them to SQL 2008 then as I
understand they will be upgraded to 2008 format I I won't be able to attach
them later to SQL 200 server.
From time to time new companies show their interest in using my application.
I wouldn't want to restrict them with SQL Server version. Existing customers
are using all versions of SQL from 2000 to 2008. I would like to keep this
for future potential customers.
Is there any feature in SQL Server 2008 allowing to attach 2000 version
database without upgrading its format?
Maybe you can suggest any other scenario for using Windows 7 and SQL 2000.
For now everything I could create it is 2 different machines with identical
lists of development tools. It is very inconvenient to make changes in 2 the
same databases, just with different versions.

Thank you
vovan

vovan (v@v.com) writes:
You install a virtual machine on your Win7 box, and then you run XP
in that VM, and run in SQL 2000 in that environment.



--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

Thank you

"Erland Sommarskog" <esquel (AT) sommarskog (DOT) se> wrote

I tried that scenario. I never store any data on the primary partition. SQL
Server 2000 setup unfortunately doesn't see any drive except A, C and D
(DVD-ROM). I was not able to find any way to install SQL Server with data
located not on primary partition.
Any other idea how to setup SQL 2000 on Windows 7?

vovan


"Erland Sommarskog" <esquel (AT) sommarskog (DOT) se> wrote

vovan (v@v.com) writes:
What disks does your virtual machine have? What virtualisation software
do you use? (I have only used VMware myself.)




--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

I tried Windows Virtual PC and VMWare. Both of them see all drives I have on
my machines. On one of them I have A, C, D, E, F, G(DVD-Rom), H(DVD-Rom), on
another one I have A, C, D, E (DVD-ROM), F(DVD-ROM). All these disks are
available when I just use them via Windows Explorer in virtual machines. But
when I'm installing SQL Server 2000, and want to change the default path for
data from disk C to another disk, all disks except C are not visible. If I
try to use existing disks as network disks, I can map existing drive, but
when I click OK, the path C:\Program Files\SQL Server... is not changed.
I decided to install SQL Server with default paths and later attach my DBs
located on other than C drives. In this case SQL Server Enterprise Manager
gives me just drive C for selection. No other drives are visible.
In VMWare I tried to create a Shared Older on one of the drive (not C). That
folder becomes visible in WMWare itself, but still invisible for SQL Server
setup as well for SQL Server Enterprise Manager.

You said you used VMWare. Did you install SQL 2000?

Thank you
vovan

"Erland Sommarskog" <esquel (AT) sommarskog (DOT) se> wrote

Hello Vovan,

by default, you can't put SQL databases on shared/network drives, maybe
this document helps: http://support.microsoft.com/kb/304261/EN-US/

Regards, Thomas


vovan schrieb:
> all disks except C are not visible.

OK, then how do I put databases on any drive, but not C? All drives are
accessible inside of Virtual Machine and outside of SQL Server, but are not
visible inside of SQL Server.

Thank you.
vovan

"Thomas Hütter" <thomas_huetter (AT) t-online (DOT) de> wrote

vovan (vcha (AT) hotmail (DOT) com) writes:
But are all these disks local to the virtual machine? If only C is local
to the virtual machine? You can only install on local disks. Similiarly,
you can only have databases on local disks.

If you are trying to put things on the local disks of your host OS,
this is not going to work out.

Yes. I did not change the install disk, but I have a database on my E disk.
(Which is a local disk in my virtual machine.)

--
Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx

How did you make E disk to be local for VM? After I read that it is not
possible to place DBs on shared drives, I tried to attach drives to VM, or
maybe not attach, but I tried to find the way to see drives from SQL running
on VM.
Now I have Enterprise Manager with several registered servers (local and a
couple of production servers). Will I be able to create a similar structure
in VM or I'm just waisting my time?

Thank you.
vovan