Viewing 15 posts - 5,596 through 5,610 (of 49,571 total)
Welsh Corgi (6/12/2015)
So you can install SSMS on the Server?
In Server Core installation, no, but since you should never be using SSMS on the server, that's hardly a large problem.
June 12, 2015 at 10:36 am
Can you confirm that restoring to yesterday is acceptable?
If you can (and ONLY if that's completely acceptable), then try taking the DB offline and bringing it back online. It may...
June 12, 2015 at 10:31 am
Please don't cross post.
Replies to http://www.sqlservercentral.com/Forums/Topic1694123-2799-1.aspx please.
June 12, 2015 at 10:05 am
Considering that no one should be using SSMS directly on the server anyway, that's a very minor concern.
June 12, 2015 at 10:02 am
This is actually pretty nasty. You've hit a bug where the log reservation wasn't enough for a rollback. That's not supposed to happen.
What backups do you have and what is...
June 12, 2015 at 10:00 am
ScottPletcher (6/12/2015)
Again, add another log file to the db, and do it quickly.
Can't add files to a DB that's RECOVERY_PENDING, it's not online, it can't be opened.
June 12, 2015 at 9:57 am
Normal, expected behaviour. Nothing to troubleshoot, nothing wrong.
Don't use Task Manager to look at SQL's memory usage, it lies. Use perfmon counters, total server memory.
June 12, 2015 at 7:57 am
Anything else in the error log? If you're not sure, post the entire contents from the time the DB ran out of space until now.
June 12, 2015 at 7:17 am
Sure, in the catch block before you THROW, use the ERROR_NUMBER(), ERROR_MESSAGE(), ERROR_PROCEDURE(), ERROR_SEVERITY() and ERROR_LINE() in an insert statement into the table of your choice.
June 12, 2015 at 6:48 am
DBA From The Cold (6/12/2015)
I thought that 112 was not enough space on disk?
Ack, you're right. Mixed it up with OS error 32.
June 12, 2015 at 6:47 am
dax.latchford (6/12/2015)
2015-06-12 05:36:39.59 spid293 D:\Database\Log\gems_ews\gems_ews_log.ldf: Operating system error 112(failed to retrieve text for this...
June 12, 2015 at 6:40 am
Flailing around and trying stuff at random's a great way to make matters worse and possibly even destroy the database. The first step in any corruption or similar scenario MUST...
June 12, 2015 at 6:37 am
You knew the IDs were unique, SQL didn't so it had to take wider locks than it would have if you'd had a unique index there in the first place.
June 12, 2015 at 6:23 am
Open up the error log, find and post all messages relating to this database. Do nothing else at this point.
June 12, 2015 at 6:22 am
Put a unique nonclustered index on the LockedBy column.
It can be a filtered index since not all rows will be locked, and the default for a row that isn't locked...
June 12, 2015 at 5:07 am
Viewing 15 posts - 5,596 through 5,610 (of 49,571 total)