Moving Sql2000 databases to 2005 one by one

Sorry for cross-posting!
We need to migrate our SQLserver2K one by one to a new server with
SQLserver2005.
I plan to create an empty database in 05' with the same name of that of 2K,
create a backup for 2K database and then restore it in 05. Will it work?
If not, what is the process to do this correctly and safely?
Thanks a million.
Bill
Use SQL Server Upgrade Advisor before migarting.
You can backup/restore or detach/attach databases.
Change compatibility level to 90 after migrating databse on SQL Server
2005
Regards
Amish Shah
|||Bill,
You should be able to either take a backup under 2000 and then just restore
this backup to 2005 or detach from 2000 and attach the original MDF/LDF or a
copied version to 2005.
Use the Upgrade Advisor to see that the code works under 2005 (90 compat)
first.
Chris Wood
"Bill nguyen" <billn_nospam_please@.jaco.com> wrote in message
news:%235al72zUGHA.5108@.TK2MSFTNGP09.phx.gbl...
> Sorry for cross-posting!
> We need to migrate our SQLserver2K one by one to a new server with
> SQLserver2005.
> I plan to create an empty database in 05' with the same name of that of
> 2K, create a backup for 2K database and then restore it in 05. Will it
> work?
> If not, what is the process to do this correctly and safely?
> Thanks a million.
> Bill
>
|||Which server I should install Upgrade Advisor? The new one (running 05) or
the old one (running 2000)?
I just did a backup/restore withour running Upgrade advisor. All tables and
views look ok, but I got error trying to ope Database diagram because "the
database doesn't have a valid owner!"
Where do I need to go to change the compatibility level?
Thanks
BN
"amish" <shahamishm@.gmail.com> wrote in message
news:1143649568.136416.302840@.g10g2000cwb.googlegr oups.com...
> Use SQL Server Upgrade Advisor before migarting.
> You can backup/restore or detach/attach databases.
> Change compatibility level to 90 after migrating databse on SQL Server
> 2005
>
> Regards
> Amish Shah
>
sql

Moving Sql2000 databases to 2005 one by one

Sorry for cross-posting!
We need to migrate our SQLserver2K one by one to a new server with
SQLserver2005.
I plan to create an empty database in 05' with the same name of that of 2K,
create a backup for 2K database and then restore it in 05. Will it work?
If not, what is the process to do this correctly and safely?
Thanks a million.
BillUse SQL Server Upgrade Advisor before migarting.
You can backup/restore or detach/attach databases.
Change compatibility level to 90 after migrating databse on SQL Server
2005
Regards
Amish Shah|||Bill,
You should be able to either take a backup under 2000 and then just restore
this backup to 2005 or detach from 2000 and attach the original MDF/LDF or a
copied version to 2005.
Use the Upgrade Advisor to see that the code works under 2005 (90 compat)
first.
Chris Wood
"Bill nguyen" <billn_nospam_please@.jaco.com> wrote in message
news:%235al72zUGHA.5108@.TK2MSFTNGP09.phx.gbl...
> Sorry for cross-posting!
> We need to migrate our SQLserver2K one by one to a new server with
> SQLserver2005.
> I plan to create an empty database in 05' with the same name of that of
> 2K, create a backup for 2K database and then restore it in 05. Will it
> work?
> If not, what is the process to do this correctly and safely?
> Thanks a million.
> Bill
>|||Which server I should install Upgrade Advisor? The new one (running 05) or
the old one (running 2000)?
I just did a backup/restore withour running Upgrade advisor. All tables and
views look ok, but I got error trying to ope Database diagram because "the
database doesn't have a valid owner!"
Where do I need to go to change the compatibility level?
Thanks
BN
"amish" <shahamishm@.gmail.com> wrote in message
news:1143649568.136416.302840@.g10g2000cwb.googlegroups.com...
> Use SQL Server Upgrade Advisor before migarting.
> You can backup/restore or detach/attach databases.
> Change compatibility level to 90 after migrating databse on SQL Server
> 2005
>
> Regards
> Amish Shah
>|||Chris;
I got this error message trying to restore the backup (from old server -
SQL2000) to new server (SQL2005):
TITLE: Microsoft SQL Server Management Studio
--
Restore failed for Server 'SQLSERVER1'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The backup set holds a backup of a database
other than the existing 'gasstation' database. (Microsoft.SqlServer.Smo)
Please help!!
Bill
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ubgoi%230UGHA.5092@.TK2MSFTNGP10.phx.gbl...
> Bill,
> You should be able to either take a backup under 2000 and then just
> restore this backup to 2005 or detach from 2000 and attach the original
> MDF/LDF or a copied version to 2005.
> Use the Upgrade Advisor to see that the code works under 2005 (90 compat)
> first.
> Chris Wood
> "Bill nguyen" <billn_nospam_please@.jaco.com> wrote in message
> news:%235al72zUGHA.5108@.TK2MSFTNGP09.phx.gbl...
>|||Chris,
I am trying to migrate from SQL 7 to SQL 2005. I also get an error when I
try to restore
my SQL 7 backup to SQL 2005. Your link did not work. I get an error when I
click on
it as well.
I also took a different route by just using the import and export function
in both SQLs.
This was working fine until I got to a table that had a field longer than 50
chars. For
some reason I get an error "Status value 4" and the import fails. If I
reduce the size of
the field to 50 or less it works fine. How do I get the import procedure to
except field sizes
larger than 50 chars?
Thanks
"Bill Nguyen" wrote:

> Chris;
> I got this error message trying to restore the backup (from old server -
> SQL2000) to new server (SQL2005):
> TITLE: Microsoft SQL Server Management Studio
> --
> Restore failed for Server 'SQLSERVER1'. (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> System.Data.SqlClient.SqlError: The backup set holds a backup of a databas
e
> other than the existing 'gasstation' database. (Microsoft.SqlServer.Smo)
> Please help!!
> Bill
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:ubgoi%230UGHA.5092@.TK2MSFTNGP10.phx.gbl...
>
>|||Chris,
I am trying to migrate from SQL 7 to SQL 2005. I also get an error when I
try to restore
my SQL 7 backup to SQL 2005. Your link did not work. I get an error when I
click on
it as well.
I also took a different route by just using the import and export function
in both SQLs.
This was working fine until I got to a table that had a field longer than 50
chars. For
some reason I get an error "Status value 4" and the import fails. If I
reduce the size of
the field to 50 or less it works fine. How do I get the import procedure to
except field sizes
larger than 50 chars?
Thanks
"Bill Nguyen" wrote:

> Chris;
> I got this error message trying to restore the backup (from old server -
> SQL2000) to new server (SQL2005):
> TITLE: Microsoft SQL Server Management Studio
> --
> Restore failed for Server 'SQLSERVER1'. (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...er&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> System.Data.SqlClient.SqlError: The backup set holds a backup of a databas
e
> other than the existing 'gasstation' database. (Microsoft.SqlServer.Smo)
> Please help!!
> Bill
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:ubgoi%230UGHA.5092@.TK2MSFTNGP10.phx.gbl...
>
>|||I don't use the GUI for these tasks. Typically, I would just do 'restore
filelistonly' and 'restore headeronly' to get the info about the backup set.
Then I do 'restore database <db> ... with replace, move...'
I suggest you take a look at bookonline for these commands and try them out.
-oj
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:1AA68C0A-71FE-44E4-BD07-4B2B09DC4AC1@.microsoft.com...[vbcol=seagreen]
> Chris,
> I am trying to migrate from SQL 7 to SQL 2005. I also get an error when I
> try to restore
> my SQL 7 backup to SQL 2005. Your link did not work. I get an error when
> I
> click on
> it as well.
> I also took a different route by just using the import and export function
> in both SQLs.
> This was working fine until I got to a table that had a field longer than
> 50
> chars. For
> some reason I get an error "Status value 4" and the import fails. If I
> reduce the size of
> the field to 50 or less it works fine. How do I get the import procedure
> to
> except field sizes
> larger than 50 chars?
> Thanks
> "Bill Nguyen" wrote:
>

Moving Sql2000 databases to 2005 one by one

Sorry for cross-posting!
We need to migrate our SQLserver2K one by one to a new server with
SQLserver2005.
I plan to create an empty database in 05' with the same name of that of 2K,
create a backup for 2K database and then restore it in 05. Will it work?
If not, what is the process to do this correctly and safely?
Thanks a million.
BillUse SQL Server Upgrade Advisor before migarting.
You can backup/restore or detach/attach databases.
Change compatibility level to 90 after migrating databse on SQL Server
2005
Regards
Amish Shah|||Bill,
You should be able to either take a backup under 2000 and then just restore
this backup to 2005 or detach from 2000 and attach the original MDF/LDF or a
copied version to 2005.
Use the Upgrade Advisor to see that the code works under 2005 (90 compat)
first.
Chris Wood
"Bill nguyen" <billn_nospam_please@.jaco.com> wrote in message
news:%235al72zUGHA.5108@.TK2MSFTNGP09.phx.gbl...
> Sorry for cross-posting!
> We need to migrate our SQLserver2K one by one to a new server with
> SQLserver2005.
> I plan to create an empty database in 05' with the same name of that of
> 2K, create a backup for 2K database and then restore it in 05. Will it
> work?
> If not, what is the process to do this correctly and safely?
> Thanks a million.
> Bill
>|||Which server I should install Upgrade Advisor? The new one (running 05) or
the old one (running 2000)?
I just did a backup/restore withour running Upgrade advisor. All tables and
views look ok, but I got error trying to ope Database diagram because "the
database doesn't have a valid owner!"
Where do I need to go to change the compatibility level?
Thanks
BN
"amish" <shahamishm@.gmail.com> wrote in message
news:1143649568.136416.302840@.g10g2000cwb.googlegroups.com...
> Use SQL Server Upgrade Advisor before migarting.
> You can backup/restore or detach/attach databases.
> Change compatibility level to 90 after migrating databse on SQL Server
> 2005
>
> Regards
> Amish Shah
>|||Chris;
I got this error message trying to restore the backup (from old server -
SQL2000) to new server (SQL2005):
TITLE: Microsoft SQL Server Management Studio
--
Restore failed for Server 'SQLSERVER1'. (Microsoft.SqlServer.Smo)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
--
ADDITIONAL INFORMATION:
System.Data.SqlClient.SqlError: The backup set holds a backup of a database
other than the existing 'gasstation' database. (Microsoft.SqlServer.Smo)
Please help!!
Bill
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:ubgoi%230UGHA.5092@.TK2MSFTNGP10.phx.gbl...
> Bill,
> You should be able to either take a backup under 2000 and then just
> restore this backup to 2005 or detach from 2000 and attach the original
> MDF/LDF or a copied version to 2005.
> Use the Upgrade Advisor to see that the code works under 2005 (90 compat)
> first.
> Chris Wood
> "Bill nguyen" <billn_nospam_please@.jaco.com> wrote in message
> news:%235al72zUGHA.5108@.TK2MSFTNGP09.phx.gbl...
>> Sorry for cross-posting!
>> We need to migrate our SQLserver2K one by one to a new server with
>> SQLserver2005.
>> I plan to create an empty database in 05' with the same name of that of
>> 2K, create a backup for 2K database and then restore it in 05. Will it
>> work?
>> If not, what is the process to do this correctly and safely?
>> Thanks a million.
>> Bill
>>
>|||Chris,
I am trying to migrate from SQL 7 to SQL 2005. I also get an error when I
try to restore
my SQL 7 backup to SQL 2005. Your link did not work. I get an error when I
click on
it as well.
I also took a different route by just using the import and export function
in both SQLs.
This was working fine until I got to a table that had a field longer than 50
chars. For
some reason I get an error "Status value 4" and the import fails. If I
reduce the size of
the field to 50 or less it works fine. How do I get the import procedure to
except field sizes
larger than 50 chars?
Thanks
"Bill Nguyen" wrote:
> Chris;
> I got this error message trying to restore the backup (from old server -
> SQL2000) to new server (SQL2005):
> TITLE: Microsoft SQL Server Management Studio
> --
> Restore failed for Server 'SQLSERVER1'. (Microsoft.SqlServer.Smo)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
> --
> ADDITIONAL INFORMATION:
> System.Data.SqlClient.SqlError: The backup set holds a backup of a database
> other than the existing 'gasstation' database. (Microsoft.SqlServer.Smo)
> Please help!!
> Bill
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:ubgoi%230UGHA.5092@.TK2MSFTNGP10.phx.gbl...
> > Bill,
> >
> > You should be able to either take a backup under 2000 and then just
> > restore this backup to 2005 or detach from 2000 and attach the original
> > MDF/LDF or a copied version to 2005.
> >
> > Use the Upgrade Advisor to see that the code works under 2005 (90 compat)
> > first.
> >
> > Chris Wood
> >
> > "Bill nguyen" <billn_nospam_please@.jaco.com> wrote in message
> > news:%235al72zUGHA.5108@.TK2MSFTNGP09.phx.gbl...
> >> Sorry for cross-posting!
> >>
> >> We need to migrate our SQLserver2K one by one to a new server with
> >> SQLserver2005.
> >>
> >> I plan to create an empty database in 05' with the same name of that of
> >> 2K, create a backup for 2K database and then restore it in 05. Will it
> >> work?
> >> If not, what is the process to do this correctly and safely?
> >>
> >> Thanks a million.
> >>
> >> Bill
> >>
> >>
> >
> >
>
>|||I don't use the GUI for these tasks. Typically, I would just do 'restore
filelistonly' and 'restore headeronly' to get the info about the backup set.
Then I do 'restore database <db> ... with replace, move...'
I suggest you take a look at bookonline for these commands and try them out.
-oj
"Ron" <Ron@.discussions.microsoft.com> wrote in message
news:1AA68C0A-71FE-44E4-BD07-4B2B09DC4AC1@.microsoft.com...
> Chris,
> I am trying to migrate from SQL 7 to SQL 2005. I also get an error when I
> try to restore
> my SQL 7 backup to SQL 2005. Your link did not work. I get an error when
> I
> click on
> it as well.
> I also took a different route by just using the import and export function
> in both SQLs.
> This was working fine until I got to a table that had a field longer than
> 50
> chars. For
> some reason I get an error "Status value 4" and the import fails. If I
> reduce the size of
> the field to 50 or less it works fine. How do I get the import procedure
> to
> except field sizes
> larger than 50 chars?
> Thanks
> "Bill Nguyen" wrote:
>> Chris;
>> I got this error message trying to restore the backup (from old server -
>> SQL2000) to new server (SQL2005):
>> TITLE: Microsoft SQL Server Management Studio
>> --
>> Restore failed for Server 'SQLSERVER1'. (Microsoft.SqlServer.Smo)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476
>> --
>> ADDITIONAL INFORMATION:
>> System.Data.SqlClient.SqlError: The backup set holds a backup of a
>> database
>> other than the existing 'gasstation' database. (Microsoft.SqlServer.Smo)
>> Please help!!
>> Bill
>>
>> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
>> news:ubgoi%230UGHA.5092@.TK2MSFTNGP10.phx.gbl...
>> > Bill,
>> >
>> > You should be able to either take a backup under 2000 and then just
>> > restore this backup to 2005 or detach from 2000 and attach the original
>> > MDF/LDF or a copied version to 2005.
>> >
>> > Use the Upgrade Advisor to see that the code works under 2005 (90
>> > compat)
>> > first.
>> >
>> > Chris Wood
>> >
>> > "Bill nguyen" <billn_nospam_please@.jaco.com> wrote in message
>> > news:%235al72zUGHA.5108@.TK2MSFTNGP09.phx.gbl...
>> >> Sorry for cross-posting!
>> >>
>> >> We need to migrate our SQLserver2K one by one to a new server with
>> >> SQLserver2005.
>> >>
>> >> I plan to create an empty database in 05' with the same name of that
>> >> of
>> >> 2K, create a backup for 2K database and then restore it in 05. Will it
>> >> work?
>> >> If not, what is the process to do this correctly and safely?
>> >>
>> >> Thanks a million.
>> >>
>> >> Bill
>> >>
>> >>
>> >
>> >
>>

moving reports to another server

I had plan to move reports from one server (reporting service) to another
server (another reporting service).
Is there any ways to move reports instead of uploading all reports (rdl)
again into another server?
As far as I know, rdl is the xml file.
after uploading to reporting what is really happen on reporting service?
where does the rdl file go after uploading (publishing) ?
ThanksSimple method is to use the deployment configuration screen (ie right click
on the project and properties) change the server name in the URL,it will get
deployed on to the other server. You can have scripts as well. basically when
you upload or deploy it builds and encrypts and stores in the database.
Amarnath
"MS newsgroup" wrote:
> I had plan to move reports from one server (reporting service) to another
> server (another reporting service).
> Is there any ways to move reports instead of uploading all reports (rdl)
> again into another server?
> As far as I know, rdl is the xml file.
> after uploading to reporting what is really happen on reporting service?
> where does the rdl file go after uploading (publishing) ?
> Thanks
>
>|||so, then
I need at least upload or deploy rdl files to reporting service.'
Is it possible to export data (ie data in dbo.Catalog or something
else)from current sql server used for reporting service to the other sql
server which use another reporting service ?
"Amarnath" <Amarnath@.discussions.microsoft.com> wrote in message
news:9A0F43E3-90FB-4C2D-A8C9-72EF10F03E89@.microsoft.com...
> Simple method is to use the deployment configuration screen (ie right
> click
> on the project and properties) change the server name in the URL,it will
> get
> deployed on to the other server. You can have scripts as well. basically
> when
> you upload or deploy it builds and encrypts and stores in the database.
> Amarnath
>
> "MS newsgroup" wrote:
>> I had plan to move reports from one server (reporting service) to another
>> server (another reporting service).
>> Is there any ways to move reports instead of uploading all reports (rdl)
>> again into another server?
>> As far as I know, rdl is the xml file.
>> after uploading to reporting what is really happen on reporting service?
>> where does the rdl file go after uploading (publishing) ?
>> Thanks
>>|||Detailed instructions:
http://support.microsoft.com/default.aspx?scid=842425
If you don't have subscriptions and extensive security customization (for
instance certain reports or folders have different rights) then redeploying
is the easiest. Otherwise follow the instructions in the above link.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"MS newsgroup" <klee@.jeromegroup.com> wrote in message
news:uMu9xEBBHHA.1224@.TK2MSFTNGP04.phx.gbl...
> so, then
> I need at least upload or deploy rdl files to reporting service.'
> Is it possible to export data (ie data in dbo.Catalog or something
> else)from current sql server used for reporting service to the other sql
> server which use another reporting service ?
>
>
>
> "Amarnath" <Amarnath@.discussions.microsoft.com> wrote in message
> news:9A0F43E3-90FB-4C2D-A8C9-72EF10F03E89@.microsoft.com...
>> Simple method is to use the deployment configuration screen (ie right
>> click
>> on the project and properties) change the server name in the URL,it will
>> get
>> deployed on to the other server. You can have scripts as well. basically
>> when
>> you upload or deploy it builds and encrypts and stores in the database.
>> Amarnath
>>
>> "MS newsgroup" wrote:
>> I had plan to move reports from one server (reporting service) to
>> another
>> server (another reporting service).
>> Is there any ways to move reports instead of uploading all reports (rdl)
>> again into another server?
>> As far as I know, rdl is the xml file.
>> after uploading to reporting what is really happen on reporting service?
>> where does the rdl file go after uploading (publishing) ?
>> Thanks
>>
>

Moving production server to new box

I'm moving my prod server to a new box. Is the plan below
workable ?
I install the new server at the same SP level as the old
server.
I copy the mdf and ldf files to the new location.
I over write the mdf and ldf files for master with the old
servers copy.
I restart the server.
Since the directory structure is different, I assume that
master will come up but other db's will be suspect.
I update sysdatbases to point to the correct path for the
user databases.
I restart the server.
Is this too simplistic 'Please read this article, and do not move or overwrite MDF/LDF files with
the server shut down!:
http://support.microsoft.com/?kbid=224071
"Jack A" <anonymous@.discussions.microsoft.com> wrote in message
news:1411901c41370$84d51b00$a301280a@.phx
.gbl...
> I'm moving my prod server to a new box. Is the plan below
> workable ?
> I install the new server at the same SP level as the old
> server.
> I copy the mdf and ldf files to the new location.
> I over write the mdf and ldf files for master with the old
> servers copy.
> I restart the server.
> Since the directory structure is different, I assume that
> master will come up but other db's will be suspect.
> I update sysdatbases to point to the correct path for the
> user databases.
> I restart the server.
> Is this too simplistic '
>|||A silly question but why not just use the Copy Database Wizard ?
http://msdn.microsoft.com/library/d...>
wiz_0z50.asp
J
-- Jack A wrote: --
I'm moving my prod server to a new box. Is the plan below
workable ?
I install the new server at the same SP level as the old
server.
I copy the mdf and ldf files to the new location.
I over write the mdf and ldf files for master with the old
servers copy.
I restart the server.
Since the directory structure is different, I assume that
master will come up but other db's will be suspect.
I update sysdatbases to point to the correct path for the
user databases.
I restart the server.
Is this too simplistic '|||Can i use this to move from a Sql 7 to Sql 2000. How do I
start the wizard. Cant find it anywhere in the interface.
>--Original Message--
>A silly question but why not just use the Copy Database
Wizard ?
>http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/adminsql/ad_onmigwiz_0z50.asp
>J
> -- Jack A wrote: --
> I'm moving my prod server to a new box. Is the plan
below
> workable ?
> I install the new server at the same SP level as the
old
> server.
> I copy the mdf and ldf files to the new location.
> I over write the mdf and ldf files for master with
the old
> servers copy.
> I restart the server.
> Since the directory structure is different, I assume
that
> master will come up but other db's will be suspect.
> I update sysdatbases to point to the correct path
for the
> user databases.
> I restart the server.
> Is this too simplistic '
>
>.
>|||The problem is if you have different path for the system databases. Move mas
ter and when you then start SQL
Server, it will look for model and tempdb in the *old* path, which might not
exists and SQL Server will not
start if it can't find these databases...
Moving SQL Server Databases
http://www.support.microsoft.com/?id=224071
Moving Databases between Servers
http://www.support.microsoft.com/?id=314546
Using WITH MOVE in a Restore to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465
How To Transfer Logins and Passwords Between SQL Servers
http://www.support.microsoft.com/?id=246133
Mapping Logins & SIDs after a Restore
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
How to Resolve Permission Issues When a Database Is Moved Between SQL Server
s
http://www.support.microsoft.com/?id=240872
User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
Disaster Recovery Articles for SQL Server
http://www.support.microsoft.com/?id=307775
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"Jack A" <anonymous@.discussions.microsoft.com> wrote in message
news:1411901c41370$84d51b00$a301280a@.phx
.gbl...
> I'm moving my prod server to a new box. Is the plan below
> workable ?
> I install the new server at the same SP level as the old
> server.
> I copy the mdf and ldf files to the new location.
> I over write the mdf and ldf files for master with the old
> servers copy.
> I restart the server.
> Since the directory structure is different, I assume that
> master will come up but other db's will be suspect.
> I update sysdatbases to point to the correct path for the
> user databases.
> I restart the server.
> Is this too simplistic '
>|||HI
SQL 2000 Enterprise Manager: click 'Run a Wizard' button (or tools menu - Wi
zards...). Expand 'Management' and select 'Copy Database Wizard'.
Select a Source Server: Your old SQL 7.0 server. ...
-- Jack A wrote: --
Can i use this to move from a Sql 7 to Sql 2000. How do I
start the wizard. Cant find it anywhere in the interface.
>--Original Message--
>A silly question but why not just use the Copy Database
Wizard ?
url=/library/en-us/adminsql/ad_onmigwiz_0z50.asp
below
> workable ?
old
> server.
> I over write the mdf and ldf files for master with
the old
> servers copy.
> I restart the server.
> Since the directory structure is different, I assume
that
> master will come up but other db's will be suspect.
> I update sysdatbases to point to the correct path
for the
> user databases.
> I restart the server.
>

Moving my SQL Server to another computer

I will moving my SQL Server to another server. The plan is to stop SQL Server copy database file to a temp netwokr location, Switch off this server. Configure the new server with the same name and IP, install SQL to the same paths and service pack to the same level (SQL 2000 sp3). Then start and stop the SQL server. Once stop I will then copy the old database file over the new ones.

I know in general this works as I have doen this many times before expect this time round there is a replicaiton database which is new, I am expecting this will work the same but has any one else tried this before?

Unfortunately, you have to disable the publication before you can detach and move the database.

BTW, I recommend you to detach the database before you move the database file to another server, this ensure you can attach it to the new server even though it is missing the transaction log file.

Moving Jobs

How can I move scheduled jobs and DB Maintgenance Plan from one server to
another?
Thanks
Emma
Emma,
DTS has a Transfer Jobs Task. As for the DB Maintenance Plans...I'm not
sure.
HTH
Jerry
"Emma" <Emma@.discussions.microsoft.com> wrote in message
news:DE64BBD5-F072-476C-B2F0-E3D3E510247A@.microsoft.com...
> How can I move scheduled jobs and DB Maintgenance Plan from one server to
> another?
> Thanks
> Emma
|||DB maintenance plans have to be re-created on each server. That is one
reason I prefer to do the same tasks in scripts.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Emma" <Emma@.discussions.microsoft.com> wrote in message
news:DE64BBD5-F072-476C-B2F0-E3D3E510247A@.microsoft.com...
> How can I move scheduled jobs and DB Maintgenance Plan from one server to
> another?
> Thanks
> Emma

Moving Jobs

How can I move scheduled jobs and DB Maintgenance Plan from one server to
another?
Thanks
EmmaEmma,
DTS has a Transfer Jobs Task. As for the DB Maintenance Plans...I'm not
sure.
HTH
Jerry
"Emma" <Emma@.discussions.microsoft.com> wrote in message
news:DE64BBD5-F072-476C-B2F0-E3D3E510247A@.microsoft.com...
> How can I move scheduled jobs and DB Maintgenance Plan from one server to
> another?
> Thanks
> Emma|||DB maintenance plans have to be re-created on each server. That is one
reason I prefer to do the same tasks in scripts.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Emma" <Emma@.discussions.microsoft.com> wrote in message
news:DE64BBD5-F072-476C-B2F0-E3D3E510247A@.microsoft.com...
> How can I move scheduled jobs and DB Maintgenance Plan from one server to
> another?
> Thanks
> Emma

Moving Jobs

How can I move scheduled jobs and DB Maintgenance Plan from one server to
another?
Thanks
EmmaEmma,
DTS has a Transfer Jobs Task. As for the DB Maintenance Plans...I'm not
sure.
HTH
Jerry
"Emma" <Emma@.discussions.microsoft.com> wrote in message
news:DE64BBD5-F072-476C-B2F0-E3D3E510247A@.microsoft.com...
> How can I move scheduled jobs and DB Maintgenance Plan from one server to
> another?
> Thanks
> Emma|||DB maintenance plans have to be re-created on each server. That is one
reason I prefer to do the same tasks in scripts.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Emma" <Emma@.discussions.microsoft.com> wrote in message
news:DE64BBD5-F072-476C-B2F0-E3D3E510247A@.microsoft.com...
> How can I move scheduled jobs and DB Maintgenance Plan from one server to
> another?
> Thanks
> Emma