Re: Enterprise to Standard
- From: "Arnie Rowland" <arnie@xxxxxxxx>
- Date: Tue, 18 Jul 2006 22:38:00 -0700
This is for a 'heads-up' awareness. For a more detailed outline see:
http://support.microsoft.com/default.aspx?scid=kb;en-us;246133
http://vyaskn.tripod.com/moving_sql_server.htm
Detach the databases, then after some of the following prep work, re-attach
them.
You will need to transfer logins, etc.
SQL Agent Jobs are located in MSDB and should be scripted out.
Any objects intentionally (or unintentionally) created in master need to be
scripted out.
--
Arnie Rowland
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"dusty" <dusty@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:245417BD-8014-4FFD-AB47-584A632B0CE4@xxxxxxxxxxxxxxxx
Because of License issues, I will be uninstalling SQL Server 2000 EE, and
installing SQL Svr 2000 SE (Win 2k Adv Svr). There are two instances
running
on my current configuration. I will include only one of the two instances
on
the new install to SE.
I have read about detaching & attaching when moving the database from one
server to another, but I really haven't found any hard information about
my
upcoming task.
My plans were to backup the databases, uninstall EE, install SE (with same
instance name that was running on EE), and restore databases.
As far as my database backup, I will simply copy the database folder to
another location, as well as my backup folder. When restoring the
databases,
should I use the mdf or .BAK files?
Will all of my login accounts transfer or will I have to re-create them
again? Is there anything that I left out or should consider before I
begin
this task?
TIA
.
- Prev by Date: Re: Set database file folder/directory at install
- Next by Date: Re: SQL Server 2005 Enterprise License Question
- Previous by thread: Re: Set database file folder/directory at install
- Next by thread: Re: Enterprise to Standard
- Index(es):
Relevant Pages
|
