SQL Server Management Studio: hardware

Showing posts with label hardware. Show all posts

Wednesday, March 28, 2012

Migrating DTS packages and SQL Jobs

Hello All,
We are in the process of migrating our SQLServer2000 production server to a
better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
that needs to be migrated as well. I can script the Jobs and run the script
on the new server and similarly I can save the DTS package on the new server.
Instead, Can I backup the msdb database and restore it on the new server. I
was wondering which method would be the best.
Thanks,
rgnRestoring MSDB is certainly an option but if you have anything that
references the original server name directly you may have to fix that.
These links may help:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/features/mssql/article.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/columnists/cBunch/movingyouruserswiththeirdatabases.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scripts/contributions/1598.asp Script
Roles and Permissions
--
Andrew J. Kelly SQL MVP
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:798481FC-6AD6-461C-A554-AF99EBD5B3E7@.microsoft.com...
> Hello All,
> We are in the process of migrating our SQLServer2000 production server to
> a
> better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
> that needs to be migrated as well. I can script the Jobs and run the
> script
> on the new server and similarly I can save the DTS package on the new
> server.
> Instead, Can I backup the msdb database and restore it on the new server.
> I
> was wondering which method would be the best.
> Thanks,
> rgn

Migrating DTS packages and SQL Jobs

Hello All,
We are in the process of migrating our SQLServer2000 production server to a
better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
that needs to be migrated as well. I can script the Jobs and run the script
on the new server and similarly I can save the DTS package on the new server
.
Instead, Can I backup the msdb database and restore it on the new server. I
was wondering which method would be the best.
Thanks,
rgnRestoring MSDB is certainly an option but if you have anything that
references the original server name directly you may have to fix that.
These links may help:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/feat...cle.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/col...se
s.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scr...utions/1598.asp Script
Roles and Permissions
Andrew J. Kelly SQL MVP
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:798481FC-6AD6-461C-A554-AF99EBD5B3E7@.microsoft.com...
> Hello All,
> We are in the process of migrating our SQLServer2000 production server to
> a
> better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
> that needs to be migrated as well. I can script the Jobs and run the
> script
> on the new server and similarly I can save the DTS package on the new
> server.
> Instead, Can I backup the msdb database and restore it on the new server.
> I
> was wondering which method would be the best.
> Thanks,
> rgn

Migrating DTS packages and SQL Jobs

Hello All,
We are in the process of migrating our SQLServer2000 production server to a
better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
that needs to be migrated as well. I can script the Jobs and run the script
on the new server and similarly I can save the DTS package on the new server.
Instead, Can I backup the msdb database and restore it on the new server. I
was wondering which method would be the best.
Thanks,
rgn
Restoring MSDB is certainly an option but if you have anything that
references the original server name directly you may have to fix that.
These links may help:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/features/mssql/article.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/columnists/cBunch/movingyouruserswiththeirdatabases.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scripts/contributions/1598.asp Script
Roles and Permissions
Andrew J. Kelly SQL MVP
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:798481FC-6AD6-461C-A554-AF99EBD5B3E7@.microsoft.com...
> Hello All,
> We are in the process of migrating our SQLServer2000 production server to
> a
> better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
> that needs to be migrated as well. I can script the Jobs and run the
> script
> on the new server and similarly I can save the DTS package on the new
> server.
> Instead, Can I backup the msdb database and restore it on the new server.
> I
> was wondering which method would be the best.
> Thanks,
> rgn
sql

Monday, March 26, 2012

Migrating an app from one cluster to another .. with the same name

Currently migrating a SQL application from an old Win2k cluster to some new
hardware.
The new hardware will run as a Win2K3SP1 cluster.
The App people would like to keep the names the same for all servers and
virtual services so that clients are not affected.
Downtime is not an option.
Whats the easiest way to do this?
Consider a DNS alias.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"Rory Niland" <RoryNiland@.discussions.microsoft.com> wrote in message
news:DDCB983B-3F22-4360-8E07-91B02887ABB3@.microsoft.com...
Currently migrating a SQL application from an old Win2k cluster to some new
hardware.
The new hardware will run as a Win2K3SP1 cluster.
The App people would like to keep the names the same for all servers and
virtual services so that clients are not affected.
Downtime is not an option.
Whats the easiest way to do this?
|||Agreed, because you can't rename a SQL machine.
Cheers,
Rod
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://www.msmvps.com/clustering - Blog
"Tom Moreau" <tom@.dont.spam.me.cips.ca> wrote in message
news:OvlMaCNcFHA.580@.TK2MSFTNGP15.phx.gbl...
> Consider a DNS alias.
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Columnist, SQL Server Professional
> Toronto, ON Canada
> www.pinpub.com
> .
> "Rory Niland" <RoryNiland@.discussions.microsoft.com> wrote in message
> news:DDCB983B-3F22-4360-8E07-91B02887ABB3@.microsoft.com...
> Currently migrating a SQL application from an old Win2k cluster to some
> new
> hardware.
> The new hardware will run as a Win2K3SP1 cluster.
> The App people would like to keep the names the same for all servers and
> virtual services so that clients are not affected.
> Downtime is not an option.
> Whats the easiest way to do this?
>

migrating a SQL Cluster to new hardware

I need your advise on migrating a two node SQL 2000 cluster to new hardware
including servers and disks.
thanks.
Amila
Create a new cluster with the new hardware, install a SQL instance, and then
migrate the databases over to the new instance (e.g. following steps in
http://vyaskn.tripod.com/moving_sql_server.htm and its referenced articles).
If the shared drives are presented from a SAN, you can remove the drives
from the cluster, create a new cluster, install a SQL instance in exactly the
same way as the existing SQL instance, and present the shared drives to the
new cluster.
If you can afford the downtime, and want to keep the server names, you can
remove the shared drives (LUNs), deactivate the cluster nodes, create a new
cluster with the same node names, cluster names, and virtual server names,
install a SQL instance, and present the same LUNs to the new cluster. The new
SQL instance can come up exactly the same as the previous one.
You may also try to perform the so-called rolling upgrade, i.e. upgrade one
node to new hardware a time.
Which method to choose depends on your upgrade requirements.
Linchi
"Amila chandrasekera" wrote:

> I need your advise on migrating a two node SQL 2000 cluster to new hardware
> including servers and disks.
>
> thanks.
> Amila
>
>
|||We have done both of what Linchi suggested: new system build/disk migration
versus node rebuild/upgrade.
The new cluster build is cleaner/easier, but then your applications have to
be migrated to the new host name (unless you can incur the long outage).
The node rebuild/upgrade is not quite as clean, but it minimizes the impact
to your end users.
Check out the maintenance and troubleshooting sections of the following
guide. There is also a link at the top that directs you to the 2005 doc as
well. Read both.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx#E14AG
The short sequence is:
Uninstall passive node from the sql server setup.
Evict passive node from cluster administrator.
Rebuild passive node.
Join rebuilt node through cluster administrator.
Install rebuilt node to sql server setup.
Patch sql server rebuilt node to current patch + hotfix as active node.
Move over resources and repeat for each cluster node.
Sincerely,
Anthony Thomas

"Amila chandrasekera" <achandra@.insight.com> wrote in message
news:%23h6t5u7SHHA.412@.TK2MSFTNGP02.phx.gbl...
> I need your advise on migrating a two node SQL 2000 cluster to new
hardware
> including servers and disks.
>
> thanks.
> Amila
>
|||Run upgrade advisor to detect upgrade issues, run checkdb on the databases
on the clusters, detach them, copy them (do not move them) to the new
cluster, attach them, run checkdb, update statistics, back them up. Migrate
all dependencies (logins, jobs, extended stored procedures, com objects and
file paths).
Check all functionality on the new cluster. Roll back if you have to by
reattaching the existing database on the old cluster.
repoint the client applications.
You might want to review all methods to do this in the
http://download.microsoft.com/download/1/6/c/16c0ec7a-bb53-4aea-9020-cb2f80424322/SQL2005UpgradeTechRef.doc
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Amila chandrasekera" <achandra@.insight.com> wrote in message
news:%23h6t5u7SHHA.412@.TK2MSFTNGP02.phx.gbl...
>I need your advise on migrating a two node SQL 2000 cluster to new hardware
>including servers and disks.
>
> thanks.
> Amila
>
|||Thanks for the replies so far. This migration is from SQL 2000 to SQL 2000
(both source and target are running on Windows 2003 Advanced server). I am
not planning to do a SQL 2005 upgrade with this migration. It is purely a
hardware upgrade only.
Here is what I am thinking of doing.
Asume Node1 and Node2 are the current production SQL cluster nodes.
Node3 and Node4 are the new servers.
1. Move all cluster roles to Node1
2. Evict node2 from the cluster
3. Conect Node3 and join it to the cluster
4. Move all cluster roles to Node3
5. Evict Node1 from cluster
6. Connect Node4 and join it to the cluster
7. Connect Node3 and Node4 to the new SAN (while connected to the old SAN )
8. Setup Quorum and data stores in the new SAN
9. Move Quorum to the new SAN
10. Shutdown the SQL Server
11. Copy SQL DBs from old SAN to the new SAN. Change Drive letter mappings
to maintain the paths.
12. Disconnect old SAN connection completely.
13. Start SQL Server
Is this feasible ? Am I missing anything here ?
"Amila chandrasekera" <achandra@.insight.com> wrote in message
news:%23h6t5u7SHHA.412@.TK2MSFTNGP02.phx.gbl...
>I need your advise on migrating a two node SQL 2000 cluster to new hardware
>including servers and disks.
>
> thanks.
> Amila
>
|||Before eviting the nodes, you have to run the SQL installer to remove the
node from the SQL cluster configuration. You cn run it afterwards and force
it out, but that takes longer. You also have to run the installer and
install SQL to the new nodes. You then need to re-apply any service packs.
GNH
"Amila chandrasekera" <achandra@.insight.com> wrote in message
news:OGAFgGFUHHA.1212@.TK2MSFTNGP03.phx.gbl...
> Thanks for the replies so far. This migration is from SQL 2000 to SQL 2000
> (both source and target are running on Windows 2003 Advanced server). I am
> not planning to do a SQL 2005 upgrade with this migration. It is purely a
> hardware upgrade only.
> Here is what I am thinking of doing.
> Asume Node1 and Node2 are the current production SQL cluster nodes.
> Node3 and Node4 are the new servers.
> 1. Move all cluster roles to Node1
> 2. Evict node2 from the cluster
> 3. Conect Node3 and join it to the cluster
> 4. Move all cluster roles to Node3
> 5. Evict Node1 from cluster
> 6. Connect Node4 and join it to the cluster
> 7. Connect Node3 and Node4 to the new SAN (while connected to the old
> SAN )
> 8. Setup Quorum and data stores in the new SAN
> 9. Move Quorum to the new SAN
> 10. Shutdown the SQL Server
> 11. Copy SQL DBs from old SAN to the new SAN. Change Drive letter mappings
> to maintain the paths.
> 12. Disconnect old SAN connection completely.
> 13. Start SQL Server
> Is this feasible ? Am I missing anything here ?
>
> "Amila chandrasekera" <achandra@.insight.com> wrote in message
> news:%23h6t5u7SHHA.412@.TK2MSFTNGP02.phx.gbl...
>
|||How Can I remove SQL after evicting the node ?
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OQ5q9KFUHHA.1180@.TK2MSFTNGP05.phx.gbl...
> Before eviting the nodes, you have to run the SQL installer to remove the
> node from the SQL cluster configuration. You cn run it afterwards and
> force it out, but that takes longer. You also have to run the installer
> and install SQL to the new nodes. You then need to re-apply any service
> packs.
> GNH
>
> "Amila chandrasekera" <achandra@.insight.com> wrote in message
> news:OGAFgGFUHHA.1212@.TK2MSFTNGP03.phx.gbl...
>
|||Go ahead and run the installer on the remaining node. When you remove the
evicted node from SQL the installer will time out and isue a warning, but it
will remove it from the SQL configuration.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Amila chandrasekera" <achandra@.insight.com> wrote in message
news:e9erf1pVHHA.3568@.TK2MSFTNGP06.phx.gbl...
> How Can I remove SQL after evicting the node ?
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OQ5q9KFUHHA.1180@.TK2MSFTNGP05.phx.gbl...
>
|||You can also remove it manually, but the Best Practice is to use the SQL
Server setup instead.
http://support.microsoft.com/kb/290991/en-us
Sincerely,
Anthony Thomas

"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:O84Iu3qVHHA.4964@.TK2MSFTNGP06.phx.gbl...
> Go ahead and run the installer on the remaining node. When you remove the
> evicted node from SQL the installer will time out and isue a warning, but
it[vbcol=seagreen]
> will remove it from the SQL configuration.
>
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "Amila chandrasekera" <achandra@.insight.com> wrote in message
> news:e9erf1pVHHA.3568@.TK2MSFTNGP06.phx.gbl...
the[vbcol=seagreen]
installer[vbcol=seagreen]
service[vbcol=seagreen]
migration.
>

Friday, March 23, 2012

Migrate SQL Server 2000 to a new server

Hi all
My organisation has SQL Server 2000 running on Windows 2000.
We've just had most of our hardware replaced and SQL Server needs to
be transferred to a better machine running Windows Server 2003.
Are there any tools that could help in doing that? In my
understanding, the databases themselves can simply be backed up and
restored on the new machine. But how can all the existing settings,
users and roles be copied to the new server?
ThanksHi Manu,
You may want to take a look at this article. It includes information on how
to move databases, logins and passwords, jobs, DTS packages, etc.
How to move databases between computers that are running SQL Server
http://support.microsoft.com/kb/314546/
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Manu" wrote:
> Hi all
> My organisation has SQL Server 2000 running on Windows 2000.
> We've just had most of our hardware replaced and SQL Server needs to
> be transferred to a better machine running Windows Server 2003.
> Are there any tools that could help in doing that? In my
> understanding, the databases themselves can simply be backed up and
> restored on the new machine. But how can all the existing settings,
> users and roles be copied to the new server?
> Thanks
>|||On Dec 14, 1:13 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
wrote:
> Hi Manu,
> You may want to take a look at this article. It includes information on how
> to move databases, logins and passwords, jobs, DTS packages, etc.
> How to move databases between computers that are running SQL Serverhttp://support.microsoft.com/kb/314546/
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
> "Manu" wrote:
> > Hi all
> > My organisation has SQL Server 2000 running on Windows 2000.
> > We've just had most of our hardware replaced and SQL Server needs to
> > be transferred to a better machine running Windows Server 2003.
> > Are there any tools that could help in doing that? In my
> > understanding, the databases themselves can simply be backed up and
> > restored on the new machine. But how can all the existing settings,
> > users and roles be copied to the new server?
> > Thanks
Hi Ben
Thanks for the reply.
According to the link, in order to transfer usernames and passwords to
SQL Server running on a different machine, the instance should be
running under a domain account. But that is not the case with our
setup. SQL Server is running under local machine accounts.
Any thoughts?
Thanks|||Manu,
That is only for the DTS Transfer Logins Tasks. You can still use the method
1 of the section 'A complete resolution to transfer logins and passwords
between different versions of SQL Server' and will get the additional benefit
of transfering the original login SID.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Manu" wrote:
> On Dec 14, 1:13 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
> wrote:
> > Hi Manu,
> >
> > You may want to take a look at this article. It includes information on how
> > to move databases, logins and passwords, jobs, DTS packages, etc.
> >
> > How to move databases between computers that are running SQL Serverhttp://support.microsoft.com/kb/314546/
> >
> > Hope this helps,
> >
> > Ben Nevarez
> > Senior Database Administrator
> > AIG SunAmerica
> >
> > "Manu" wrote:
> > > Hi all
> >
> > > My organisation has SQL Server 2000 running on Windows 2000.
> > > We've just had most of our hardware replaced and SQL Server needs to
> > > be transferred to a better machine running Windows Server 2003.
> >
> > > Are there any tools that could help in doing that? In my
> > > understanding, the databases themselves can simply be backed up and
> > > restored on the new machine. But how can all the existing settings,
> > > users and roles be copied to the new server?
> >
> > > Thanks
> Hi Ben
> Thanks for the reply.
> According to the link, in order to transfer usernames and passwords to
> SQL Server running on a different machine, the instance should be
> running under a domain account. But that is not the case with our
> setup. SQL Server is running under local machine accounts.
> Any thoughts?
> Thanks
>|||Manu
http://vyaskn.tripod.com/moving_sql_server.htm
"Manu" <mandeep.sekhon@.gmail.com> wrote in message
news:839ffaa6-d07f-4f5a-a224-4f338dbb55ff@.s19g2000prg.googlegroups.com...
> Hi all
> My organisation has SQL Server 2000 running on Windows 2000.
> We've just had most of our hardware replaced and SQL Server needs to
> be transferred to a better machine running Windows Server 2003.
> Are there any tools that could help in doing that? In my
> understanding, the databases themselves can simply be backed up and
> restored on the new machine. But how can all the existing settings,
> users and roles be copied to the new server?
> Thanks|||On Dec 17, 3:06 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Manuhttp://vyaskn.tripod.com/moving_sql_server.htm
> "Manu" <mandeep.sek...@.gmail.com> wrote in message
> news:839ffaa6-d07f-4f5a-a224-4f338dbb55ff@.s19g2000prg.googlegroups.com...
> > Hi all
> > My organisation has SQL Server 2000 running on Windows 2000.
> > We've just had most of our hardware replaced and SQL Server needs to
> > be transferred to a better machine running Windows Server 2003.
> > Are there any tools that could help in doing that? In my
> > understanding, the databases themselves can simply be backed up and
> > restored on the new machine. But how can all the existing settings,
> > users and roles be copied to the new server?
> > Thanks
Hi Uri
Thanks for the reply.
The link that you sent me requires that SQL Server be running on the
same operating system on both the machines.
In my case, however, the OS is changing too. The new machine runs
Windows Server 2003 while the older one was running Windows 2000.|||On Dec 14, 6:09 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
wrote:
> Manu,
> That is only for the DTS Transfer Logins Tasks. You can still use the method
> 1 of the section 'A complete resolution to transfer logins and passwords
> between different versions of SQL Server' and will get the additional benefit
> of transfering the original login SID.
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
> "Manu" wrote:
> > On Dec 14, 1:13 pm, Ben Nevarez <BenNeva...@.discussions.microsoft.com>
> > wrote:
> > > Hi Manu,
> > > You may want to take a look at this article. It includes information on how
> > > to move databases, logins and passwords, jobs, DTS packages, etc.
> > > How to move databases between computers that are running SQL Serverhttp://support.microsoft.com/kb/314546/
> > > Hope this helps,
> > > Ben Nevarez
> > > Senior Database Administrator
> > > AIG SunAmerica
> > > "Manu" wrote:
> > > > Hi all
> > > > My organisation has SQL Server 2000 running on Windows 2000.
> > > > We've just had most of our hardware replaced and SQL Server needs to
> > > > be transferred to a better machine running Windows Server 2003.
> > > > Are there any tools that could help in doing that? In my
> > > > understanding, the databases themselves can simply be backed up and
> > > > restored on the new machine. But how can all the existing settings,
> > > > users and roles be copied to the new server?
> > > > Thanks
> > Hi Ben
> > Thanks for the reply.
> > According to the link, in order to transfer usernames and passwords to
> > SQL Server running on a different machine, the instance should be
> > running under a domain account. But that is not the case with our
> > setup. SQL Server is running under local machine accounts.
> > Any thoughts?
> > Thanks
Hi Ben
That worked beautifully.
As mentioned on the web page, default databases assigned to the logins
are different.
Is there any way to assign the default databases apart from writing a
script using 'sp_defaultdb' for each login?
Regards

Wednesday, March 28, 2012

Migrating DTS packages and SQL Jobs

Migrating DTS packages and SQL Jobs

Migrating DTS packages and SQL Jobs

Monday, March 26, 2012

Migrating an app from one cluster to another .. with the same name

migrating a SQL Cluster to new hardware

Friday, March 23, 2012

Migrate SQL Server 2000 to a new server

Migrate SQL Server 2000 to a new server

Migrate SQL Server 2000 to a new server

SQL Server Management Studio

Blog Archive

About Me