Wednesday, March 21, 2012

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:
>

No comments:

Post a Comment