Moving a SQL Server to a new domain?

Can anyone point me in the right direction here?
What do I need to be aware of when moving a SQL 2000 server from a 2000 to a
different 2003 domain (not upgrading the existing domain)? The server has
roughly 40 SQL users and they are all configured to use SQL Authentication.
Is it as simple as removing the server from one domain and joining the other
with some possible workstation configuration changes to reflect the new FQDN?
Thanks in advance!If it was 6.5, then you would have lots of work. But 2000 is fairly
transparent. The only thing you can have to do is recreate the login because
their GUID changed on the new domain.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"FombyJambox" wrote:
> Can anyone point me in the right direction here?
> What do I need to be aware of when moving a SQL 2000 server from a 2000 to a
> different 2003 domain (not upgrading the existing domain)? The server has
> roughly 40 SQL users and they are all configured to use SQL Authentication.
> Is it as simple as removing the server from one domain and joining the other
> with some possible workstation configuration changes to reflect the new FQDN?
> Thanks in advance!

Moving a SQL Server 2005 Cluster from one Domain to another

First, Can you move a SQL Server 2005 Cluster from one active directory domain to another? If so, what are the steps in moving a SQL Server 2005 Cluster from one domain to another?

Are there any concerns in attempting that move? I know that the domain groups are a hard dependency and that you cannot change them without doing a full reinstall. Does this have any bearing to moving a cluster between domains?

Thank you in advance for you assistance.

David P

Hey David...did you review the following 2 kb articles, they lay the process and possible pitfalls out pretty well:

How to move a Windows Cluster Server from one domain to another

http://support.microsoft.com/kb/269196/

How to change domains for a SQL Server 2000 or SQL Server 2005 failover cluster

http://support.microsoft.com/default.aspx/kb/319016/en-us#appliesto

If you review and have further questions, just post back.

HTH

Moving a DB to a different domain and then connecting

If a thief yanks (technical term) a hard-drive containing a SQL Server 05 database from a server and then installs it on a server in a different domain, is there any way he could connect to it? This question assumes that a hacker didn't somehow transfer the domain logins.

Could the local admin even add himself as a user to the database without having the admin login information from the previous domain?

Thanks,

As the server is attached by a sysadmin (no matter if its a malicious domain :-) ) the sysadmin will have full access to the database. Thats why the access to the physical files also has to be secured rather than just the logical access through autorization.

See this recently answered post: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=801002&SiteID=1

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Moving a cluster out of a domain

I need to move my cluster out of a domain and into a
workgroup. Is there any documentation available on this
procedure? So far an online search has come up empty.
You must have a domain (AD or NT4) for a cluster. The cluster needs a
common security context for all the services to work correctly. You cannot
run a cluster in a workgroup environment.
Geoff N. Hiten
Microsoft SQL Server MVP.
"Scott" <anonymous@.discussions.microsoft.com> wrote in message
news:195901c55498$4652f090$a601280a@.phx.gbl...
>I need to move my cluster out of a domain and into a
> workgroup. Is there any documentation available on this
> procedure? So far an online search has come up empty.
|||The cluster was originally set up by Dell when we got the
hardware in a workgroup. Unfortunately our support with
them has expired which is why I am searching online.
I believe they had a DNS server running on the cluster that
allowed it to work.

>--Original Message--
>You must have a domain (AD or NT4) for a cluster. The
cluster needs a
>common security context for all the services to work
correctly. You cannot
>run a cluster in a workgroup environment.
>Geoff N. Hiten
>Microsoft SQL Server MVP.
>
>"Scott" <anonymous@.discussions.microsoft.com> wrote in
message
>news:195901c55498$4652f090$a601280a@.phx.gbl...
>
>.
>
|||Doesn't change the fact that you must have a domain account for the cluster
service account. If you wish to move from one domain to another, you should
read the following KB for details about recreating the cluster service
account:
http://support.microsoft.com/kb/269229
Again, MSCS does not work in a workgroup.
Regards,
John
<anonymous@.discussions.microsoft.com> wrote in message
news:15ab01c5549b$e4c8b4f0$a401280a@.phx.gbl...[vbcol=seagreen]
> The cluster was originally set up by Dell when we got the
> hardware in a workgroup. Unfortunately our support with
> them has expired which is why I am searching online.
> I believe they had a DNS server running on the cluster that
> allowed it to work.
> cluster needs a
> correctly. You cannot
> message

move SQL 2000 server to new AD domain

Hello,
We have aquired a new company and I need to migrate a SQL 2000 server from
thier existing domain to our AD domain. Other than changing the service
accounts and any SQL domain accounts is there anything else I should be aware
of?
old domain: nt4
new domain: 2000 native
SQL server: win 2k advanced, SQl 2000 std.
thanks!Hi
If you are renaming the server as well as moving domain (same name in the
new domain should be ok) you will need to drop the server and re-create it
using sp_dropserver and sp_addserver see
http://support.microsoft.com/kb/303774
If you have windows logins then you will need to migrate those see
http://support.microsoft.com/kb/246133/
John
"decipher" wrote:
> Hello,
> We have aquired a new company and I need to migrate a SQL 2000 server from
> thier existing domain to our AD domain. Other than changing the service
> accounts and any SQL domain accounts is there anything else I should be aware
> of?
> old domain: nt4
> new domain: 2000 native
> SQL server: win 2k advanced, SQl 2000 std.
> thanks!

Move SQL 2000 server from workgroup to a domain

I have been asked to move a system running MS SQL 2000 Server from a workgroup to a domain. The SQL server is running in SQL Authentication and the services are running as local system.

Will SQL Server break after the move?

Any advice will help. I thought I remember this being the case, but possibly only with Windows Authentication.

As always it's best to test before you try something like this on a Production server, but you should not have any problems. If SQL Server is running under Local System, that should not impact anything because Local System will still be there after you join the domain. As far as any SQL authentication accounts, they should not be impacted either because they are local accounts to SQL whether or not the server is in a Workgroup or a Domain.

With that said, test, test, and test

|||Nope, it will not break. This is transparent to SQL Server. The only thing that matters is the service account. Other accounts can be configured to use domain accounts once the move has been completed|||

Thanks for the advice. I thought it would be ok, but I just wanted to get some additional thoughts on the matter.

Cheers.

|||I have this project in plan that going to migrate SQL Login authentication into Windows authentication with AD integrate. But I worried about those application user ID, Task Scheduler, DTS package that created by using SQL account. So does it will affect those user ID login once integrate into AD windows authentication.

Any idea where can find the proper sulotion on the net?

move db from sql2000 to 2005sp1

I have sql2000 db that had two domain groups in the dbo role and one SQL
acct also in the dbo role. There are only tables in the db and all owned by
dbo, I am not sure if the developers created the tables and then changed the
owner or specified on creation. I restored the db to sql2005sp1 and setup
the logins via the sp_helprevlogins and now crap has hit the fan.
1) The domain group can login to SQL but when one of them clicks on the
user tables to expand they get the error:
Failed to retrieve data for this request (Microsoft.sql.server.smoenum)
Additional Information:
Am exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.sqlserver.connectioninfo)
Select permission denied on object 'extended properties', database
mssqlsystemresource', schema 'sys'.(Microsoft sql server, error 329)
I know the one that is having the issue is the one that created the tables.
Others in the domain group can see the tables.
2) Others in group that can see the table, when they try and create a new
table and get the following error:
Property DefaultSchema is not available for the Database '[XXXXDB]'. This
property may not exist for this object, or may not be retrievable due to
insufficient access rights. (sqleditors)
I guess I am missing something.
Thanks
CHi
It sounds like your upgrade procedure has not given the users the correct
permissions. I would expect all users within the same domain group to have
the same problems, therefore Iif they get different problems they are
probably in different groups.
Do you really want to grant such wide permissions to so many users? If you
created a database role with the minimum number of permissions you require
then the domain group could be added to that. In which case dropping the
domain group as a login and adding it again would not be an issue.
You may want to use GRANT LOGIN when you add the groups rather than
sp_addlogin.
John
"CD" wrote:
> I have sql2000 db that had two domain groups in the dbo role and one SQL
> acct also in the dbo role. There are only tables in the db and all owned by
> dbo, I am not sure if the developers created the tables and then changed the
> owner or specified on creation. I restored the db to sql2005sp1 and setup
> the logins via the sp_helprevlogins and now crap has hit the fan.
>
> 1) The domain group can login to SQL but when one of them clicks on the
> user tables to expand they get the error:
>
> Failed to retrieve data for this request (Microsoft.sql.server.smoenum)
> Additional Information:
> Am exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.sqlserver.connectioninfo)
> Select permission denied on object 'extended properties', database
> mssqlsystemresource', schema 'sys'.(Microsoft sql server, error 329)
>
> I know the one that is having the issue is the one that created the tables.
> Others in the domain group can see the tables.
>
> 2) Others in group that can see the table, when they try and create a new
> table and get the following error:
>
> Property DefaultSchema is not available for the Database '[XXXXDB]'. This
> property may not exist for this object, or may not be retrievable due to
> insufficient access rights. (sqleditors)
>
>
> I guess I am missing something.
>
> Thanks
> C
>
>|||Thanks for the reply, no actually the group constist of 3 domain accts with
the group being the database pre-defined dbo role, only one of them can not
see the table objects. I know this one created the tables on the sql2000
side and then changed the owner of the tables to dbo (error 1 note). The
other 2 accounts can see all the tables but can not create a new one.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:9A9CE67E-59B0-4A5B-A797-4F02FCCD9A7C@.microsoft.com...
> Hi
> It sounds like your upgrade procedure has not given the users the correct
> permissions. I would expect all users within the same domain group to have
> the same problems, therefore Iif they get different problems they are
> probably in different groups.
> Do you really want to grant such wide permissions to so many users? If you
> created a database role with the minimum number of permissions you require
> then the domain group could be added to that. In which case dropping the
> domain group as a login and adding it again would not be an issue.
> You may want to use GRANT LOGIN when you add the groups rather than
> sp_addlogin.
> John
> "CD" wrote:
>> I have sql2000 db that had two domain groups in the dbo role and one SQL
>> acct also in the dbo role. There are only tables in the db and all owned
>> by
>> dbo, I am not sure if the developers created the tables and then changed
>> the
>> owner or specified on creation. I restored the db to sql2005sp1 and
>> setup
>> the logins via the sp_helprevlogins and now crap has hit the fan.
>>
>> 1) The domain group can login to SQL but when one of them clicks on the
>> user tables to expand they get the error:
>>
>> Failed to retrieve data for this request (Microsoft.sql.server.smoenum)
>> Additional Information:
>> Am exception occurred while executing a Transact-SQL statement or batch.
>> (Microsoft.sqlserver.connectioninfo)
>> Select permission denied on object 'extended properties', database
>> mssqlsystemresource', schema 'sys'.(Microsoft sql server, error 329)
>>
>> I know the one that is having the issue is the one that created the
>> tables.
>> Others in the domain group can see the tables.
>>
>> 2) Others in group that can see the table, when they try and create a new
>> table and get the following error:
>>
>> Property DefaultSchema is not available for the Database '[XXXXDB]'.
>> This
>> property may not exist for this object, or may not be retrievable due to
>> insufficient access rights. (sqleditors)
>>
>>
>> I guess I am missing something.
>>
>> Thanks
>> C
>>|||Hi
If there are no permissions granted directly to the group then you should
not have an issue dropping and re-creating it. The logins would not require
their own schemas. To create tables on the schemas they would require CREATE
TABLE permission on the database and ALTER permission on the schema. You
would require other permissions if you started to use XML schemas.
John
"CD" wrote:
> Thanks for the reply, no actually the group constist of 3 domain accts with
> the group being the database pre-defined dbo role, only one of them can not
> see the table objects. I know this one created the tables on the sql2000
> side and then changed the owner of the tables to dbo (error 1 note). The
> other 2 accounts can see all the tables but can not create a new one.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:9A9CE67E-59B0-4A5B-A797-4F02FCCD9A7C@.microsoft.com...
> > Hi
> >
> > It sounds like your upgrade procedure has not given the users the correct
> > permissions. I would expect all users within the same domain group to have
> > the same problems, therefore Iif they get different problems they are
> > probably in different groups.
> >
> > Do you really want to grant such wide permissions to so many users? If you
> > created a database role with the minimum number of permissions you require
> > then the domain group could be added to that. In which case dropping the
> > domain group as a login and adding it again would not be an issue.
> >
> > You may want to use GRANT LOGIN when you add the groups rather than
> > sp_addlogin.
> >
> > John
> >
> > "CD" wrote:
> >
> >> I have sql2000 db that had two domain groups in the dbo role and one SQL
> >> acct also in the dbo role. There are only tables in the db and all owned
> >> by
> >> dbo, I am not sure if the developers created the tables and then changed
> >> the
> >> owner or specified on creation. I restored the db to sql2005sp1 and
> >> setup
> >> the logins via the sp_helprevlogins and now crap has hit the fan.
> >>
> >>
> >>
> >> 1) The domain group can login to SQL but when one of them clicks on the
> >> user tables to expand they get the error:
> >>
> >>
> >>
> >> Failed to retrieve data for this request (Microsoft.sql.server.smoenum)
> >>
> >> Additional Information:
> >>
> >> Am exception occurred while executing a Transact-SQL statement or batch.
> >>
> >> (Microsoft.sqlserver.connectioninfo)
> >>
> >> Select permission denied on object 'extended properties', database
> >> mssqlsystemresource', schema 'sys'.(Microsoft sql server, error 329)
> >>
> >>
> >>
> >> I know the one that is having the issue is the one that created the
> >> tables.
> >> Others in the domain group can see the tables.
> >>
> >>
> >>
> >> 2) Others in group that can see the table, when they try and create a new
> >> table and get the following error:
> >>
> >>
> >>
> >> Property DefaultSchema is not available for the Database '[XXXXDB]'.
> >> This
> >> property may not exist for this object, or may not be retrievable due to
> >> insufficient access rights. (sqleditors)
> >>
> >>
> >>
> >>
> >>
> >> I guess I am missing something.
> >>
> >>
> >>
> >> Thanks
> >>
> >> C
> >>
> >>
> >>
>
>|||I am feeling stupid here.
But I need to get the domain\DevTeam rights to create a table. They can
alter or delete an existing but not create they get the error:
Property DefaultSchema is not available for the Database '[XXXXDB]'. This
property may not exist for this object, or may not be retrievable due to
insufficient access rights. (sqleditors)
I tried at the DB permission level setting what you desribed but get the
same error.
What am I missing here?
1) I create the user database.
2) add the group to at the SQL/Security/Logins level
2a) then on the User Mapping, check the Map to the database on the top,
check the database role of db_owner at the bottom.
What else?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6BA2DFCA-32EF-42F5-89BB-ED26646AE4F4@.microsoft.com...
> Hi
> If there are no permissions granted directly to the group then you should
> not have an issue dropping and re-creating it. The logins would not
> require
> their own schemas. To create tables on the schemas they would require
> CREATE
> TABLE permission on the database and ALTER permission on the schema. You
> would require other permissions if you started to use XML schemas.
> John|||Hi
You can not define a default schema for a windows group and this seems to
stop you using the New Table wizard in Managment Studio. You will be able to
create tables from a query window and specify the schema as dbo, therefore
eliminating any need to change the schema later. Using a role, which has the
permissions I stated in the last post then a warning will appear when you
enter the new table dialog, but it will not create the tables in the dbo
schema.
John
"CD" wrote:
> I am feeling stupid here.
> But I need to get the domain\DevTeam rights to create a table. They can
> alter or delete an existing but not create they get the error:
> Property DefaultSchema is not available for the Database '[XXXXDB]'. This
> property may not exist for this object, or may not be retrievable due to
> insufficient access rights. (sqleditors)
> I tried at the DB permission level setting what you desribed but get the
> same error.
> What am I missing here?
> 1) I create the user database.
> 2) add the group to at the SQL/Security/Logins level
> 2a) then on the User Mapping, check the Map to the database on the top,
> check the database role of db_owner at the bottom.
> What else?
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6BA2DFCA-32EF-42F5-89BB-ED26646AE4F4@.microsoft.com...
> > Hi
> >
> > If there are no permissions granted directly to the group then you should
> > not have an issue dropping and re-creating it. The logins would not
> > require
> > their own schemas. To create tables on the schemas they would require
> > CREATE
> > TABLE permission on the database and ALTER permission on the schema. You
> > would require other permissions if you started to use XML schemas.
> >
> > John
>
>

move db from sql2000 to 2005sp1

I have sql2000 db that had two domain groups in the dbo role and one SQL
acct also in the dbo role. There are only tables in the db and all owned by
dbo, I am not sure if the developers created the tables and then changed the
owner or specified on creation. I restored the db to sql2005sp1 and setup
the logins via the sp_helprevlogins and now crap has hit the fan.
1) The domain group can login to SQL but when one of them clicks on the
user tables to expand they get the error:
Failed to retrieve data for this request (Microsoft.sql.server.smoenum)
Additional Information:
Am exception occurred while executing a Transact-SQL statement or batch.
(Microsoft.sqlserver.connectioninfo)
Select permission denied on object 'extended properties', database
mssqlsystemresource', schema 'sys'.(Microsoft sql server, error 329)
I know the one that is having the issue is the one that created the tables.
Others in the domain group can see the tables.
2) Others in group that can see the table, when they try and create a new
table and get the following error:
Property DefaultSchema is not available for the Database '[XXXXDB]'. Th
is
property may not exist for this object, or may not be retrievable due to
insufficient access rights. (sqleditors)
I guess I am missing something.
Thanks
CHi
It sounds like your upgrade procedure has not given the users the correct
permissions. I would expect all users within the same domain group to have
the same problems, therefore Iif they get different problems they are
probably in different groups.
Do you really want to grant such wide permissions to so many users? If you
created a database role with the minimum number of permissions you require
then the domain group could be added to that. In which case dropping the
domain group as a login and adding it again would not be an issue.
You may want to use GRANT LOGIN when you add the groups rather than
sp_addlogin.
John
"CD" wrote:

> I have sql2000 db that had two domain groups in the dbo role and one SQL
> acct also in the dbo role. There are only tables in the db and all owned
by
> dbo, I am not sure if the developers created the tables and then changed t
he
> owner or specified on creation. I restored the db to sql2005sp1 and setup
> the logins via the sp_helprevlogins and now crap has hit the fan.
>
> 1) The domain group can login to SQL but when one of them clicks on the
> user tables to expand they get the error:
>
> Failed to retrieve data for this request (Microsoft.sql.server.smoenum)
> Additional Information:
> Am exception occurred while executing a Transact-SQL statement or batch.
> (Microsoft.sqlserver.connectioninfo)
> Select permission denied on object 'extended properties', database
> mssqlsystemresource', schema 'sys'.(Microsoft sql server, error 329)
>
> I know the one that is having the issue is the one that created the tables
.
> Others in the domain group can see the tables.
>
> 2) Others in group that can see the table, when they try and create a new
> table and get the following error:
>
> Property DefaultSchema is not available for the Database '[XXXXDB]'.
This
> property may not exist for this object, or may not be retrievable due to
> insufficient access rights. (sqleditors)
>
>
> I guess I am missing something.
>
> Thanks
> C
>
>|||Thanks for the reply, no actually the group constist of 3 domain accts with
the group being the database pre-defined dbo role, only one of them can not
see the table objects. I know this one created the tables on the sql2000
side and then changed the owner of the tables to dbo (error 1 note). The
other 2 accounts can see all the tables but can not create a new one.
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:9A9CE67E-59B0-4A5B-A797-4F02FCCD9A7C@.microsoft.com...[vbcol=seagreen]
> Hi
> It sounds like your upgrade procedure has not given the users the correct
> permissions. I would expect all users within the same domain group to have
> the same problems, therefore Iif they get different problems they are
> probably in different groups.
> Do you really want to grant such wide permissions to so many users? If you
> created a database role with the minimum number of permissions you require
> then the domain group could be added to that. In which case dropping the
> domain group as a login and adding it again would not be an issue.
> You may want to use GRANT LOGIN when you add the groups rather than
> sp_addlogin.
> John
> "CD" wrote:
>|||Hi
If there are no permissions granted directly to the group then you should
not have an issue dropping and re-creating it. The logins would not require
their own schemas. To create tables on the schemas they would require CREATE
TABLE permission on the database and ALTER permission on the schema. You
would require other permissions if you started to use XML schemas.
John
"CD" wrote:

> Thanks for the reply, no actually the group constist of 3 domain accts wi
th
> the group being the database pre-defined dbo role, only one of them can n
ot
> see the table objects. I know this one created the tables on the sql2000
> side and then changed the owner of the tables to dbo (error 1 note). The
> other 2 accounts can see all the tables but can not create a new one.
>
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:9A9CE67E-59B0-4A5B-A797-4F02FCCD9A7C@.microsoft.com...
>
>|||I am feeling stupid here.
But I need to get the domain\DevTeam rights to create a table. They can
alter or delete an existing but not create they get the error:
Property DefaultSchema is not available for the Database '[XXXXDB]'. Th
is
property may not exist for this object, or may not be retrievable due to
insufficient access rights. (sqleditors)
I tried at the DB permission level setting what you desribed but get the
same error.
What am I missing here?
1) I create the user database.
2) add the group to at the SQL/Security/Logins level
2a) then on the User Mapping, check the Map to the database on the top,
check the database role of db_owner at the bottom.
What else?
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:6BA2DFCA-32EF-42F5-89BB-ED26646AE4F4@.microsoft.com...
> Hi
> If there are no permissions granted directly to the group then you should
> not have an issue dropping and re-creating it. The logins would not
> require
> their own schemas. To create tables on the schemas they would require
> CREATE
> TABLE permission on the database and ALTER permission on the schema. You
> would require other permissions if you started to use XML schemas.
> John|||Hi
You can not define a default schema for a windows group and this seems to
stop you using the New Table wizard in Managment Studio. You will be able to
create tables from a query window and specify the schema as dbo, therefore
eliminating any need to change the schema later. Using a role, which has the
permissions I stated in the last post then a warning will appear when you
enter the new table dialog, but it will not create the tables in the dbo
schema.
John
"CD" wrote:

> I am feeling stupid here.
> But I need to get the domain\DevTeam rights to create a table. They can
> alter or delete an existing but not create they get the error:
> Property DefaultSchema is not available for the Database '[XXXXDB]'.
This
> property may not exist for this object, or may not be retrievable due to
> insufficient access rights. (sqleditors)
> I tried at the DB permission level setting what you desribed but get the
> same error.
> What am I missing here?
> 1) I create the user database.
> 2) add the group to at the SQL/Security/Logins level
> 2a) then on the User Mapping, check the Map to the database on the top,
> check the database role of db_owner at the bottom.
> What else?
> "John Bell" <jbellnewsposts@.hotmail.com> wrote in message
> news:6BA2DFCA-32EF-42F5-89BB-ED26646AE4F4@.microsoft.com...
>
>

Move DB from Sql Server 2000 to Sql Server 2005

Hi;
How can I move a database from Sql Server 2000 to Sql Server 2005 (different
machines, same domain)?
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htmDavid Thielen wrote:
> Hi;
> How can I move a database from Sql Server 2000 to Sql Server 2005 (differe
nt
> machines, same domain)?
> --
> thanks - dave
> david_at_windward_dot_net
> http://www.windwardreports.com
> Cubicle Wars - http://www.windwardreports.com/film.htm
You can do a backup/restore or detach/attach , both the same as you
would going from sql 2000 to another sql 2000 server.|||Hi,
Add on to that;
1. You can use Copy database wizard to copy database online (no downtime)
See the below article upgrade databases from SQl 2000 to sql 2005.
http://msdn2.microsoft.com/en-us/library/ms188664.aspx
Thanks
Hari
SQL Server MVP
"Ken" <kshapley@.sbcglobal.net> wrote in message
news:1155595027.838838.10620@.h48g2000cwc.googlegroups.com...
> David Thielen wrote:
> You can do a backup/restore or detach/attach , both the same as you
> would going from sql 2000 to another sql 2000 server.
>|||Hi Dave,
Thanks for posting.
My understanding of your issue is: You want to move database from SQL 2000
to SQL 2005.
Ken & Hari provided great suggestions. Summary as:
1. Backup/Restore
2. Detach/Attach
3. Use Copy Database Wizard in SQL 2005.
These suggestions are accurate and I'd like to provide some additional
information as below:
How to: Move a Database Using Detach and Attach
http://msdn2.microsoft.com/en-us/library/ms187858.aspx
How to: Upgrade a Database Using Detach and Attach
http://msdn2.microsoft.com/en-us/library/ms189625.aspx
How to: Upgrade to SQL Server 2005 with the Copy Database Wizard
http://msdn2.microsoft.com/en-us/library/ms190775.aspx
In addition, please don't forget to transfer the login if necessary.
Please refer to following article:
246133 How to transfer logins and passwords between instances of
SQL Server
http://support.microsoft.com/defaul...kb;EN-US;246133
Hope the information helps. If you have any other concerns or questions,
please feel free to let me know. I'm glad to provide assistance.
Best regards,
Vincent Xu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
--[vbcol=seagreen]
(different[vbcol=seagreen]

Move DB from Sql Server 2000 to Sql Server 2005

Hi;
How can I move a database from Sql Server 2000 to Sql Server 2005 (different
machines, same domain)?
--
thanks - dave
david_at_windward_dot_net
http://www.windwardreports.com
Cubicle Wars - http://www.windwardreports.com/film.htmDavid Thielen wrote:
> Hi;
> How can I move a database from Sql Server 2000 to Sql Server 2005 (different
> machines, same domain)?
> --
> thanks - dave
> david_at_windward_dot_net
> http://www.windwardreports.com
> Cubicle Wars - http://www.windwardreports.com/film.htm
You can do a backup/restore or detach/attach , both the same as you
would going from sql 2000 to another sql 2000 server.|||Hi,
Add on to that;
1. You can use Copy database wizard to copy database online (no downtime)
See the below article upgrade databases from SQl 2000 to sql 2005.
http://msdn2.microsoft.com/en-us/library/ms188664.aspx
Thanks
Hari
SQL Server MVP
"Ken" <kshapley@.sbcglobal.net> wrote in message
news:1155595027.838838.10620@.h48g2000cwc.googlegroups.com...
> David Thielen wrote:
>> Hi;
>> How can I move a database from Sql Server 2000 to Sql Server 2005
>> (different
>> machines, same domain)?
>> --
>> thanks - dave
>> david_at_windward_dot_net
>> http://www.windwardreports.com
>> Cubicle Wars - http://www.windwardreports.com/film.htm
> You can do a backup/restore or detach/attach , both the same as you
> would going from sql 2000 to another sql 2000 server.
>|||Hi Dave,
Thanks for posting.
My understanding of your issue is: You want to move database from SQL 2000
to SQL 2005.
Ken & Hari provided great suggestions. Summary as:
1. Backup/Restore
2. Detach/Attach
3. Use Copy Database Wizard in SQL 2005.
These suggestions are accurate and I'd like to provide some additional
information as below:
How to: Move a Database Using Detach and Attach
http://msdn2.microsoft.com/en-us/library/ms187858.aspx
How to: Upgrade a Database Using Detach and Attach
http://msdn2.microsoft.com/en-us/library/ms189625.aspx
How to: Upgrade to SQL Server 2005 with the Copy Database Wizard
http://msdn2.microsoft.com/en-us/library/ms190775.aspx
In addition, please don't forget to transfer the login if necessary.
Please refer to following article:
246133 How to transfer logins and passwords between instances of
SQL Server
http://support.microsoft.com/default.aspx?scid=kb;EN-US;246133
Hope the information helps. If you have any other concerns or questions,
please feel free to let me know. I'm glad to provide assistance.
Best regards,
Vincent Xu
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
>>Thread-Topic: Move DB from Sql Server 2000 to Sql Server 2005
>>thread-index: Aca/74Gu4a9R8Y7PR6m3MIFjbCbRow==>>X-WBNR-Posting-Host: 69.25.210.130
>>From: =?Utf-8?B?RGF2aWQgVGhpZWxlbg==?= <thielen@.nospam.nospam>
>>Subject: Move DB from Sql Server 2000 to Sql Server 2005
>>Date: Mon, 14 Aug 2006 15:18:02 -0700
>>Lines: 13
>>Message-ID: <41275E10-6591-43F1-9C82-CA1C2FC0F131@.microsoft.com>
>>MIME-Version: 1.0
>>Content-Type: text/plain;
>> charset="Utf-8"
>>Content-Transfer-Encoding: 7bit
>>X-Newsreader: Microsoft CDO for Windows 2000
>>Content-Class: urn:content-classes:message
>>Importance: normal
>>Priority: normal
>>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.1830
>>Newsgroups: microsoft.public.sqlserver.server
>>Path: TK2MSFTNGXA01.phx.gbl
>>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:441928
>>NNTP-Posting-Host: TK2MSFTNGXA01.phx.gbl 10.40.2.250
>>X-Tomcat-NG: microsoft.public.sqlserver.server
>>Hi;
>>How can I move a database from Sql Server 2000 to Sql Server 2005
(different
>>machines, same domain)?
>>--
>>thanks - dave
>>david_at_windward_dot_net
>>http://www.windwardreports.com
>>Cubicle Wars - http://www.windwardreports.com/film.htm
>>