SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


SQL Server outof space question.


SQL Server outof space question.

Author
Message
haiao2000
haiao2000
Old Hand
Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)

Group: General Forum Members
Points: 314 Visits: 438
Lowell (4/29/2013)
hmmm; i'd say there is always files that can be moved or deleted.

files in temp folders on the operating system, log files, , the already suggested moving of backup files, so many other possibilities to address this quickly.


I agree, unfortunately I didn't even get a chance to lay my hand on the server, another engineer in the company, who work at a client site in another country asked for assistance and I am shooting in the dark.
Lowell
Lowell
One Orange Chip
One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)One Orange Chip (28K reputation)

Group: General Forum Members
Points: 28229 Visits: 39955
ouch; remote-second hand assistance is tough,

I feel for you and what headaches are involved in getting your information once-removed from the client.

Lowell

--
help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

SQL Show
SQL Show
SSChasing Mays
SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)

Group: General Forum Members
Points: 651 Visits: 1078
I had the same problem few years back, no space in ldf drive. But users were able to logon. We received error only when try to run dml statements.
SQL Show
SQL Show
SSChasing Mays
SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)SSChasing Mays (651 reputation)

Group: General Forum Members
Points: 651 Visits: 1078
sqlnaive (4/29/2013)
All the DBs were configured with Full recovery but the backups were were never taken afterwards


Correct me if am wrong. If backup never taken, then db will go into auto-truncate option, even in full recovery model.So it could not be your problem.
haiao2000
haiao2000
Old Hand
Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)

Group: General Forum Members
Points: 314 Visits: 438
The fellow coworker that asked the question has been quiet since my last suggestion, so I am guessing he was able to manage the sittuation. The last question he asked was if he can delete the LDF file and still be able to reattach the database. I told him he could, but extremely cautious and back it up before delete it permanently. I sent him query to reattach db without LDF file and that was last time I heard from him =)

Thanks everyone for your input.
OnlyOneRJ
OnlyOneRJ
Old Hand
Old Hand (346 reputation)Old Hand (346 reputation)Old Hand (346 reputation)Old Hand (346 reputation)Old Hand (346 reputation)Old Hand (346 reputation)Old Hand (346 reputation)Old Hand (346 reputation)

Group: General Forum Members
Points: 346 Visits: 690
SQL Show (4/30/2013)
I had the same problem few years back, no space in ldf drive. But users were able to logon. We received error only when try to run dml statements.


The same problem happened last week & it was so urgent that i only had sfew minutes to make it right & finnaly i tyhought of & did a Truncate Log... Shrinking option..w00t

************************************
Every Dog has a Tail !!!!! :-D
GilaMonster
GilaMonster
SSC Guru
SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)SSC Guru (87K reputation)

Group: General Forum Members
Points: 87417 Visits: 45272
haiao2000 (4/30/2013)
The last question he asked was if he can delete the LDF file and still be able to reattach the database. I told him he could, but extremely cautious and back it up before delete it permanently. I sent him query to reattach db without LDF file and that was last time I heard from him =)


I do hope he had a backup, because if you detach a DB that's got a completely full log file and then delete the transaction log, the chances are better than average that you won't be able to reattach (there wasn't space in the log for SQL to do a clean shut down) and that you'll need to fetch out a database backup and restore it.

That's why the first thing I said in this thread was "Do Not Delete the log file"

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


haiao2000
haiao2000
Old Hand
Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)

Group: General Forum Members
Points: 314 Visits: 438
OnlyOneRJ (4/30/2013)
SQL Show (4/30/2013)
I had the same problem few years back, no space in ldf drive. But users were able to logon. We received error only when try to run dml statements.


The same problem happened last week & it was so urgent that i only had sfew minutes to make it right & finnaly i tyhought of & did a Truncate Log... Shrinking option..w00t



In my case the fellow coworked stated that I couldnt truncate log even. so not sure what the deal there.
haiao2000
haiao2000
Old Hand
Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)Old Hand (314 reputation)

Group: General Forum Members
Points: 314 Visits: 438
haiao2000 (4/30/2013)
OnlyOneRJ (4/30/2013)
SQL Show (4/30/2013)
I had the same problem few years back, no space in ldf drive. But users were able to logon. We received error only when try to run dml statements.


The same problem happened last week & it was so urgent that i only had sfew minutes to make it right & finnaly i tyhought of & did a Truncate Log... Shrinking option..w00t



In my case the fellow coworked stated that I couldnt truncate log even. so not sure what the deal there.


Oh Ok I remember you mentioned that.
sqlnaive
sqlnaive
SSCarpal Tunnel
SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)SSCarpal Tunnel (4.3K reputation)

Group: General Forum Members
Points: 4285 Visits: 2774
SQL Show (4/30/2013)
sqlnaive (4/29/2013)
All the DBs were configured with Full recovery but the backups were were never taken afterwards


Correct me if am wrong. If backup never taken, then db will go into auto-truncate option, even in full recovery model.So it could not be your problem.


Nope. if you are not taking backups then log file will start growing to an extent where you will face disk issue. So once your DB has been set to bulk-logged ot full reovery, you MUST schedule log backups. Auto-truncate does not automatically gets enabled in full recovery. It is the feature in simple recovery model.

I had the same problem few years back, no space in ldf drive. But users were able to logon. We received error only when try to run dml statements.

This was because logging in is not an event that is getting written in log. In case you fire any DML, then there is the data change and that's when there is necessity to write in log file which is showing disk issue.
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search