Viewing 15 posts - 12,301 through 12,315 (of 49,558 total)
What's the text of the error the app gave? Most people don't memorise complex error numbers.
July 19, 2013 at 10:30 am
Please read through this: http://www.sqlservercentral.com/articles/Transaction+Log/72488/
July 19, 2013 at 9:34 am
sql-lover (7/19/2013)
Ran DBCC CHECKIDENT and the current column value looks like is higher than the current identity value so it will fail because next one is there.
Suggests that someone, sometime...
July 19, 2013 at 8:06 am
If you just want to know if any occur, perhaps an agent alert on error 1205?
July 19, 2013 at 7:48 am
Migrating a DB does not reseed identities. Check for jobs that may have done so, ask other DBAs, check the max value in the table and compare it to the...
July 19, 2013 at 7:47 am
Tune the queries, tune the indexes. There's no magic 'go-faster' button
Grant Frichey's written a good book on performance tuning or you can identify the problematic portion of the procedure and...
July 19, 2013 at 7:36 am
The OS time stamps on database files are meaningless.
Not familiar with either tool, so all I can guess is they're showing you different things.
July 19, 2013 at 7:33 am
Without a traceflag, there's nothing written into the SQL errorlog.
The deadlock error is sev 16, not enough to be logged. You can set up an agent alert for it or,...
July 19, 2013 at 7:31 am
Identity has never guaranteed unique numbers, just incrementing numbers. If the identity gets reseeded, SQL will start from the given number regardless of whether that number is already in the...
July 19, 2013 at 7:26 am
Without seeing the corruption messages, I can't advise in detail, but if the corruption was fatal, then the only option would have been to restore the latest usable backup. With...
July 19, 2013 at 3:55 am
HanShi (7/19/2013)
If you are able to specify on which column you are searching, then below is a simple solution:
Simple, yes, providing performance isn't a consideration.
July 19, 2013 at 1:50 am
You can't take log backups in simple recovery.
Take a normal full backup, copy it to the server you need to restore to. Restore the backup.
July 19, 2013 at 1:34 am
Chances are you're not going to be able to recover fully.
Please run the following and post the full and complete, unedited output.
DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS
July 19, 2013 at 1:32 am
Please don't cross post. It just wastes peoples time and fragments replies.
No replies to this thread please. Direct replies to: http://www.sqlservercentral.com/Forums/Topic1475281-1550-1.aspx
July 19, 2013 at 1:32 am
SQLisAwE5OmE (7/18/2013)
July 19, 2013 at 1:28 am
Viewing 15 posts - 12,301 through 12,315 (of 49,558 total)