Migrating an SQL server to another machine

Hello,
I have to migrate SQL 200o from an NT4 to a 2003 machine. I would like to
keep al the settings/users/databases intact.
How could this be acomplished?
Kind regards,
Paul.
One or more of below should get you started:
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 Servers
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
http://www.solidqualitylearning.com/
"Paul" <microsoftnews@.knipsel.nl> wrote in message news:%23CO5wfIoEHA.800@.TK2MSFTNGP14.phx.gbl...
> Hello,
> I have to migrate SQL 200o from an NT4 to a 2003 machine. I would like to
> keep al the settings/users/databases intact.
> How could this be acomplished?
> Kind regards,
>
> Paul.
>
>
|||Thanks Tibor!
This will cetainly help!
Regards,
Paul
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OXnhJvIoEHA.3324@.TK2MSFTNGP10.phx.gbl...
> One or more of below should get you started:
>
> 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
> Servers
> 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
> http://www.solidqualitylearning.com/
>
> "Paul" <microsoftnews@.knipsel.nl> wrote in message
> news:%23CO5wfIoEHA.800@.TK2MSFTNGP14.phx.gbl...
>

Migrating an SQL server to another machine

Hello,
I have to migrate SQL 200o from an NT4 to a 2003 machine. I would like to
keep al the settings/users/databases intact.
How could this be acomplished?
Kind regards,
Paul.One or more of below should get you started:
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 Servers
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
http://www.solidqualitylearning.com/
"Paul" <microsoftnews@.knipsel.nl> wrote in message news:%23CO5wfIoEHA.800@.TK2MSFTNGP14.phx.gbl...
> Hello,
> I have to migrate SQL 200o from an NT4 to a 2003 machine. I would like to
> keep al the settings/users/databases intact.
> How could this be acomplished?
> Kind regards,
>
> Paul.
>
>|||Thanks Tibor!
This will cetainly help!
Regards,
Paul
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:OXnhJvIoEHA.3324@.TK2MSFTNGP10.phx.gbl...
> One or more of below should get you started:
>
> 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
> Servers
> 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
> http://www.solidqualitylearning.com/
>
> "Paul" <microsoftnews@.knipsel.nl> wrote in message
> news:%23CO5wfIoEHA.800@.TK2MSFTNGP14.phx.gbl...
>> Hello,
>> I have to migrate SQL 200o from an NT4 to a 2003 machine. I would like to
>> keep al the settings/users/databases intact.
>> How could this be acomplished?
>> Kind regards,
>>
>> Paul.
>>
>>
>

migrate adp projects from SQL 7 to SQL 2000

We currently have a adp project linked with a Sql server 7 running NT4.
We need to replace old server with a win server 2003 with SQL 2000 sp4.
When I restore complete DB from old server to new server all objects
have (dbo) suffix and when we test the adp - through running a saved
report the report fails because it is looking for a table without the
(dbo) suffix.
Any help would be appreiciated.Not sure if I understand the question but ...
Are these linked tables? Just rename the links and that will work.
For example if the new link is dbo_Customers just rename it to Customers.
Please let us know if this was the issue or something else.
Ben Nevarez, MCDBA, OCP
Database Administrator
"dkordyban@.gmail.com" wrote:

> We currently have a adp project linked with a Sql server 7 running NT4.
> We need to replace old server with a win server 2003 with SQL 2000 sp4.
> When I restore complete DB from old server to new server all objects
> have (dbo) suffix and when we test the adp - through running a saved
> report the report fails because it is looking for a table without the
> (dbo) suffix.
> Any help would be appreiciated.
>|||Yes, SQL tables are linked to project. When viewing the tables, views
and stored procedures from the project, they all appear with (dbo)
after the object.
It may be somthing with sql 2000 sp4. I restored the exact same .bak
file to a Windows 2000 with sql 2000 sp3 and it worked fine - no (dbo)
after every object
Thanks for your time

migrate adp projects from SQL 7 to SQL 2000

We currently have a adp project linked with a Sql server 7 running NT4.
We need to replace old server with a win server 2003 with SQL 2000 sp4.
When I restore complete DB from old server to new server all objects
have (dbo) suffix and when we test the adp - through running a saved
report the report fails because it is looking for a table without the
(dbo) suffix.
Any help would be appreiciated.
Not sure if I understand the question but ...
Are these linked tables? Just rename the links and that will work.
For example if the new link is dbo_Customers just rename it to Customers.
Please let us know if this was the issue or something else.
Ben Nevarez, MCDBA, OCP
Database Administrator
"dkordyban@.gmail.com" wrote:

> We currently have a adp project linked with a Sql server 7 running NT4.
> We need to replace old server with a win server 2003 with SQL 2000 sp4.
> When I restore complete DB from old server to new server all objects
> have (dbo) suffix and when we test the adp - through running a saved
> report the report fails because it is looking for a table without the
> (dbo) suffix.
> Any help would be appreiciated.
>
|||Yes, SQL tables are linked to project. When viewing the tables, views
and stored procedures from the project, they all appear with (dbo)
after the object.
It may be somthing with sql 2000 sp4. I restored the exact same .bak
file to a windows 2000 with sql 2000 sp3 and it worked fine - no (dbo)
after every object
Thanks for your time

migrate adp projects from SQL 7 to SQL 2000

We currently have a adp project linked with a Sql server 7 running NT4.
We need to replace old server with a win server 2003 with SQL 2000 sp4.
When I restore complete DB from old server to new server all objects
have (dbo) suffix and when we test the adp - through running a saved
report the report fails because it is looking for a table without the
(dbo) suffix.
Any help would be appreiciated.Not sure if I understand the question but ...
Are these linked tables? Just rename the links and that will work.
For example if the new link is dbo_Customers just rename it to Customers.
Please let us know if this was the issue or something else.
Ben Nevarez, MCDBA, OCP
Database Administrator
"dkordyban@.gmail.com" wrote:
> We currently have a adp project linked with a Sql server 7 running NT4.
> We need to replace old server with a win server 2003 with SQL 2000 sp4.
> When I restore complete DB from old server to new server all objects
> have (dbo) suffix and when we test the adp - through running a saved
> report the report fails because it is looking for a table without the
> (dbo) suffix.
> Any help would be appreiciated.
>|||Yes, SQL tables are linked to project. When viewing the tables, views
and stored procedures from the project, they all appear with (dbo)
after the object.
It may be somthing with sql 2000 sp4. I restored the exact same .bak
file to a windows 2000 with sql 2000 sp3 and it worked fine - no (dbo)
after every object
Thanks for your time