TempDB Deleted Accidentally

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Article Discussions » Article Discussions by Author » Discuss content posted by Tushar Kanti » TempDB Deleted Accidentally

25 posts, Page 1 of 3

1 2 3 »»»

TempDB Deleted Accidentally

Rate Topic

Display Mode

Topic Options

Author

Message

tushkieeeee

Posted Tuesday, May 03, 2011 10:57 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 25, 2013 7:59 AM
Points: 103, Visits: 410

Comments posted to this topic are about the item TempDB Deleted Accidentally

Post #1102852

Mr. hoek

Posted Wednesday, May 04, 2011 12:52 AM

Valued Member

Group: General Forum Members
Last Login: Monday, April 08, 2013 7:49 AM
Points: 54, Visits: 40

Why not just 'create' the G: drive?

- ex: subst g: <anypath>

Then one does not have to run the SQL in Single User mode and such....

Post #1102896

sqlsc-790406

Posted Wednesday, May 04, 2011 12:59 AM

Grasshopper

Group: General Forum Members
Last Login: Thursday, December 08, 2011 9:44 AM
Points: 13, Visits: 14

SQL server doesn't care much where you put stuff, only that the path exist
so you could also use good old dos command SUBST e.g.:

Create a folder c:\temp\data whith the correct ntfs permissions
SUBST g: c:\temp\
Start SQL server Service
Start SSMS
move tempdb to somewhere safe
etc.
when finished:
SUBST g: /d

Rob.

Post #1102900

Perry Whittle

Posted Wednesday, May 04, 2011 1:40 AM

SSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 2:33 PM
Points: 5,201, Visits: 11,150

the article is correct, subst will not work especially if the service runs under a user account. The steps are perfectly reasonable, although i have to say this topic (starting in single user mode) has been done to death.

For reference, there is no MOVE parameter for ALTER DATABASE you should use MODIFY to alter a file or filegroup. Otherwise very tidy article, well done

-----------------------------------------------------------------------------------------------------------

"Ya can't make an omelette without breaking just a few eggs" Wink

Post #1102908

Mr. hoek

Posted Wednesday, May 04, 2011 1:54 AM

Valued Member

Group: General Forum Members
Last Login: Monday, April 08, 2013 7:49 AM
Points: 54, Visits: 40

Of course - thanks for mentioning this (sometimes one types faster then on thinks Tongue

)

Post #1102913

Resender

Posted Wednesday, May 04, 2011 1:57 AM

SSC Veteran

Group: General Forum Members
Last Login: Wednesday, March 27, 2013 8:55 AM
Points: 289, Visits: 683

I've been training to get 70-432 certification and came across this problem as well.

My personal opinion is that not only should you try and move tempdb to another location the default but his must be well documented.

Post #1102914

mohammed moinudheen

Posted Wednesday, May 04, 2011 2:19 AM

SSCrazy

Group: General Forum Members
Last Login: Thursday, May 16, 2013 3:34 PM
Points: 2,170, Visits: 3,582

Nice article, but I thought there would be something more than starting sql server in single user mode :)

Mohammed Moinudheen

Post #1102919

Peter Pirker

Posted Wednesday, May 04, 2011 2:23 AM

SSC Rookie

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 5:28 AM
Points: 36, Visits: 206

Handy article, thanks.

One cannot but admire all the brave DBA's out there who have to live with "a constant fear of losing data because of the mistakes of some developer or support person". Personally, I'm sure I couldn't handle such stress!

Although, by the sound of it, that's not exactly what happended here. More like errare humanum est, eh?

Wink

Post #1102923

tushkieeeee

Posted Wednesday, May 04, 2011 2:56 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, April 25, 2013 7:59 AM
Points: 103, Visits: 410

Thankyou All for the comments and views.
@ Perry Whittle . I just ment to move the files physically and not syntactically.
@ Grasshopper. I don not think that will be possible as pointed out already.

Tushar

Post #1102934

abhijit.vedak 76782

Posted Wednesday, May 04, 2011 3:49 AM

Grasshopper

Group: General Forum Members
Last Login: Saturday, March 02, 2013 1:15 AM
Points: 21, Visits: 65

This reminded me of something that happened a few years ago when working on SQL Server 2000. Same scenario. Following is what I did to resolve the issue:
a) Create a dummy folder (say "X") on a drive having ample space.
b) Created the same folder hierarchy (\X\Foldername) inside this folder as the path of the folder where tempdb was supposed to be located.
c) Mapped this newly created folder (X) as the drive (G-drive in this case).

On starting the SQL Server Service, it created the tempdb on this mapped G-drive which in turn was folder "\X\Foldername".

Post #1102955

« Prev Topic | Next Topic »

25 posts, Page 1 of 3

1 2 3 »»»

Permissions