Re: SQL 2005 Sept databases

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Just keep the mdf and ldf files somewhere safe. When the server is back
up simply right click the server in SSMS and choose "Attach"! You may
have to sort out orphaned users, but apart from that it should be OK.

--
Regards
Chris

Dave H wrote:

> I made some fairly large DB's (5 x 150GB) under the September CTP SQL
> Server. Is there an easy way to keep these databases and reattach
> them after I de-install the CTP and install RTM?

.

Relevant Pages

  • RE: WSUS Problems
    ... To attach a jpg or txt file to the reply, please refer to the below KB ... Name of Internet news server - msnews.microsoft.com ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • RE: Problem debugging External Assembly
    ... that I think a change I've made to a process is loaded, but in fact BizTalk ... When I attach Visual Studio to a process and enter the ... the version of the code you have is the same as the version on the server ... Remote Monitor on the server that I'm developing onto, ...
    (microsoft.public.biztalk.general)
  • Re: WSS 2.0 to 3.0 upgrade
    ... Well I ran the inplace upgrade and it didn't report any errors. ... time it took for the database to attach. ... Windows 2003 server, the SQL Server, restoring from backup to WSS 2.0, ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Drive image
    ... you only have 1 server and a couple of clients; ... This utility has a nifty feature that allows you to create an emergency boot ... > any suggestions on where to attach the external drive ... >> After you install it on a computer, you can create a boot CD. ...
    (microsoft.public.windows.server.sbs)
  • Re: The debugger component on the server failed to connect to the local machine
    ... I get the error message "Unable to attach to the process. ... The debugger ... want to attach to the remote server process. ... And I can debug the application on my local machine with IIS. ...
    (microsoft.public.vsnet.debugging)