RE: Upgrade to Window's 2008

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Yes, I think it will almost backup all the setting, to be more precise follow
these steps too…..
• Copy the data files and transaction log files from your old SQL Server's
hard drive (for example C:\MSSQL\Data) to the new SQL Server's hard drive (to
the same location, in this example, C:\MSSQL\Data). Since we are copying all
database files, including the system databases (like master, model, msdb,
distribution), your server level settings, jobs, DTS packages, alerts,
operators, logins etc. will be copied across.
• Copy all the other folders (like backup, ftdata, jobs, log, repldata etc.)
under the old server's MSSQL directory, to the same location on the new
server.
• Copy any other folders or files from the old server to the new server,
that will be accessed by your jobs, DTS packages, stored procedures etc.
• If you have any specific net library configurations, aliases, protocol
binding orders on the old server, make sure you apply those changes to the
new SQL Server, using the tools, Client Network utility and Server Network
Utility.
• Take a note of any shares on the old server, and recreate them on the new
server, with the same permissions and access rights to the relevant Windows
accounts.
• Start the SQL Server, SQL Agent and MS Search services on the new server.
Connect to the new server, using Enterprise Manager and make sure all the
databases are displayed and that there are no suspect databases. Scan through
the SQL Server error logs, SQL Agent error logs, System and Application event
logs, to make sure there are no errors. If you find any errors, fix them
before you proceed any further.

Manpreet Singh
http://crazysql.co.nr
http://crazysql.wordpress.com
MCITP – DB Admin, DB Dev SQL Server 2005
MCTS – MOSS 2007, SQL server 2005



"Lijun Zhang" wrote:

Our system administrator plan to upgrade our production SQL Server from
Window's 2003 to Window's 2008. He said as usual he does not want to do an
upgrade, he wants to do a fresh installation by pull out the C: drive and
install Window's 2008 from scratch. That means I need to install SQL Server
2005 from scratch too, which means all the server settings, logins, user
database entries, SQL Agent maintenance jobs, log shippings settings etc
need to be re-setup. I don't know how tightly SQL server master database
(and all system databases) is coupled with the operating system. Can I do
the following to preserve my current sever settings (all user databases are
not on C: drivers):

1. Disable all SQL Server Agency jobs.
2. Backup master database and MSDB before install Window's 2008.
3. Install SQL Server 2005 to the same directory as previous. Apply the
service packs and hot fixes to the same version as previous.
4. Restore master database.
5. Restore MSDB.
6. Enable all SQL Server Agency jobs.

Thanks,

Lijun



.



Relevant Pages

  • CREATE AGGREGATE failed because type Concatenate does not conform to UDAGG specification due to meth
    ... Now register the assembly and the aggregate in the SQL Server database you want ... I'm trying to do some CLR integration with sql server 2005. ...
    (microsoft.public.sqlserver.programming)
  • Re: How do i move an SQLDatabase to another location?
    ... I went to my clients and installed SQL Server ... Express and copied my database to the same location it was in while i was ... knowing that i can bring a database with me and install ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: New to Windows CE Development - Have some questions
    ... validating against the main database, or querying the database during data ... iterate through the SQL CE table and create new entries in the ... SQL Server database that correspond. ... >>> not connected to the Enterprise. ...
    (microsoft.public.windowsce.app.development)
  • RE: Logging in in background
    ... wold take all kinds of modifictions as I'd need to be checking that each SQL ... my database and all have connection strings associated with them. ... I suspect that there is also an issue on the SQL Server side as I keep ...
    (microsoft.public.access.modulesdaovba)
  • RE: SBS 2003 Unable to connect to database STS_Config
    ... MSDE to store SharePoint uses the MSSQL$SharePoint database, ... SharePoint named instance to full SQL. ... You cannot upgrade the Monitoring instance to SQL ... What I see is the SQL server group and under ...
    (microsoft.public.windows.server.sbs)