Migrate Systems Table

MS SQL SERVER

    Sponsored Links

    Next

  • 1. SQL2K instance on VMWARE ESX 3.0 on IBM SAN.
    We are in the process of implementing a farm of VMWARE ESX servers and we have decided to migrate our SQL Server instances into this environment and store the data-files of the various databases (both system's and users') on the SAN (IBM DS-4800) to which these ESX servers are attached. I am looking for pointers / hints / advice with respect to this architecture, e.g., what are the best practices of implementing SQL Server 2000 in VMWARE on a SAN, what are the important things to look after, any configuration guidelines, relevant documents, what to avoid, etc. Any contribution is welcome and will be highly appreciated. TIA, Panos Tsapralis, Athens, GREECE.
  • 2. How to redistribute the last version of sqldmo.dll?
    Hi, I would like to install the last version of sqldmo.dll (2000.85.2004.0).How this is possible?Is anybody know a redistributable MergeModule or a setup for this purpose? Regards, Ketchup
  • 3. unexpected failure during the setup - help!
    We are trying to install integration services after the fact of the passive node of a w2k3 cluster. We have tried the copy to a local drive and setup the [servers] and [tools] directories, yet we still can't get past the discovery portion of the install. Run setup.exe, received the following error message window.. "There was an unexpected failure during the setup wizard. You may review the setuplogs and/or click the Help button for more information SQL Server 2005 Standard 9.00.3042 Windows 2003 (Build 3790.srv03_sp2_rtm.070216-1710 : Service Pack 2) SQL Server has 1 virtual server installed. Details: Link ID 20476 Product Name Microsoft SQL Server Product Version 9.00.3042.00 Message Source setup.rll Message ID 50000 EvtType sqldiscovery\discoveryengine cpp@i Summary Log: Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlsval.dll Version:2005.90.3042.0 Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. WinException : -2147217389 Error Code: -2147217389 Windows Error Text: Source File Name: sqldiscovery\discoveryengine.cpp Compiler Timestamp: Wed Jun 14 16:28:21 2006 Function Name: CDiscoveryEngine::CIM_OperatingSystemProc Source Line Number: 201
  • 4. sql server 2005 64-bit on win2k3 ent. ed 64-bit
    Most DVDs \ ISOs I've seen has all versions of SQL Server 2005 (x64\ x86) Especially if you see the ITAx64 in the DVD then I would think that x64 would be on that DVD too. -- Ekrem soy "ph1sh99" < XXXX@XXXXX.COM > wrote in message news:%23$ XXXX@XXXXX.COM ... > hi, > > I am trying to install sql 2005 64-bit on my win2k3 ent. ed. 64-bit > server. the only sql dvds I have are for 32-bit and itanium. is there a > separate DVD for sql 64-bit? > > thanks >

Migrate Systems Table

Postby RWQ » Sat, 09 Dec 2006 10:09:00 GMT

Hi,
  Can anyone please give me some advice about how to migrate the systems 
table from SQL 2000 to 2005?  I am going to use side by side upgrade.  I know 
it is ok to copy/Restore or Detach / Attach for users' dbs.  I am not sure 
hot to move master, MSDB (Jobs, DTS) to 05

Thanks

Ed

Re: Migrate Systems Table

Postby Arnie Rowland » Sat, 09 Dec 2006 16:20:40 GMT

Maybe one of these articles will help:

Moving Server/Database/Logins
 http://www.**--****.com/ 
 http://www.**--****.com/ (en-US,SQL.90).aspx Moving 
system dbs 2005
 http://www.**--****.com/ 
system DB's 2000
 http://www.**--****.com/ 's between Servers
 http://www.**--****.com/ 
New Location with Detach/Attach
 http://www.**--****.com/ 

-- 
Arnie Rowland, Ph.D.
Westwood Consulting, Inc


Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous

You can't help someone get up a hill without getting a little closer to the 
top yourself.
- H. Norman Schwarzkopf









Similar Threads:

1.Migrating Systems

I am to be involved in moving 3 clusters soon from one data center in the 
Northeast to Texas.   The main requirement is to have the shortest cutover 
period possible via some kind of replicated technologies.

System 1 - 64-bit SQL Server 2000 SP4 to a like environment.   I see no 
issue with that one.  Stage the new server, restore a backup and put it in 
log shipping or use a product like Double-Take to keep things in sync. 

System 2 - 32-bit SQL Server 2000 SP3a to 64-bit SQL Server 2000 SP4.  This 
instance has over 200 databases on it.    Don't think log shipping is an 
option here.  It's not indexed well enough for replication and because the 
environments aren't like I don't think Double-Take will work.  Ideas?

System 3 - 32-bit SQL Server 7 SP4 to a 64-bit SQL Server 2000 SP4.  The SQL 
7 cluster is currently on Windows NT.   Same scenario as System 2. 

Ideas? 

2.Migrate Operating System to Windows 2003

I have Windows 2000(SP3) with Sql 2000 (SP3).

We have 50 Gbytes (Total) and 30 Data Bases in SQL 2000.

We need to migrate to Windows 2003. We can't have another machine to do the
paralel enviroment.

What the best practices to do this?

What i need to do before migrate?



Silvio Chelli


3.Migrate SQL 2000 system

Hi, there, 
I hv few questions on migrate a SQL 2000 system, details enironment are: 
1. MachineA is current live server runing SQL 2000 with SP3 on windows 2000 
server with SP4 platform. Now we bought one new server to replace the old one 
and migrate the 2000 SQL on the new server (Also running windows 2000 server 
with SP 4 with all hotfix and SQL 2000 & SP3), My planning is: Backup the 
live Database and master Database from the live server. Then restore the same 
on the new server. Is that the best solution? 
2. I hv another server currently runing SQL 2000& SP4 on windows 2000 server 
& SP4 Platform, I want migrate to SQL2005 standard Edition, I was told to 
backup the database and master DB, then uninstall SQL2000 standard edition 
and install SQL 2005, after that restore master db and user DB. 

My SQL2000 is standard Edition. 
Appreciate for any suggestion. 

Shermaine

4.determining what are "system" objects in sp_help or system tables

Hi,

I have a few things on my databases which seem to be neither true system 
objects or user objects - notably a table called 'dtproperties' (created 
by Enterprise manager as I understand, relating to relationship graphing 
or something) and some stored procs begining with "dt_" (some kind of 
source control stuff, possible visual studio related). These show up when 
I use 

"exec sp_help 'databaseName'"

but not in Ent. Mgr. or in Query Analyzer's object browser, and also not 
in a third party tool I use called AdeptSQL. I am wondering how those 
tools know to differentiate between these types of quasi-system objects, 
and my real user data. (This is for the purpose of a customized schema 
generator I am writing). I'd prefer to determine this info with system 
stored procs (ie sp_help, sp_helptex, sp_...etc) but will dip into the 
system tables if needed.


    Thanks,
    Dave



Return to MS SQL SERVER

 

Who is online

Users browsing this forum: No registered users and 39 guest