Reputation
6,425
Top tag
Next privilege 10,000 Rep.
Access moderator tools
Badges
1 8 21
Newest
 Announcer
Impact
~156k people reached

May
21
comment Sudden poor SELECT performance on a large table with existing indexes
There is a lot of stuff out there. This from Microsoft: blogs.msdn.com/b/sqlmeditation/archive/2012/12/06/…
May
21
comment Sudden poor SELECT performance on a large table with existing indexes
That's a range scan. That's what a seek does if it's returning more than one record.
May
20
comment Sudden poor SELECT performance on a large table with existing indexes
It's a total of 14k reads on log_events, on a table with 31M rows. That doesn't sound like a table scan to me. And a total of 21k reads, with CPU time less than 1% of the total time - just sounds like bad disk.
May
20
answered Sudden poor SELECT performance on a large table with existing indexes
May
17
answered Another bad execution plan!
May
10
comment Have full SQL Server restore but losing 1 day of data
That's terrific. I'm pleased. Reach out if there's ever anything you need.
May
10
comment Have full SQL Server restore but losing 1 day of data
No worries. Good luck. It's getting late here in Aus, so I'm not going to be around much longer. I'll check in later though.
May
10
comment Have full SQL Server restore but losing 1 day of data
I thought you didn't have a database. So what did you do to get something you could backup?
May
10
comment Have full SQL Server restore but losing 1 day of data
Then bring it online again. Ignore the errors. Then see if you can do a log backup.
May
10
comment Have full SQL Server restore but losing 1 day of data
Create a new database with the same name... Make sure it's in the full recovery model. Back it up so it knows it's in really in full. Then take it offline. Now rename the actual files, and swap in a copy of your file.
May
10
comment Have full SQL Server restore but losing 1 day of data
Ok. So how were you trying to back it up? There may be hope after all.
May
10
comment Have full SQL Server restore but losing 1 day of data
That is: was your old database definitely using simple?
May
10
comment Have full SQL Server restore but losing 1 day of data
Ok. How were you backing it up then?
May
10
comment Have full SQL Server restore but losing 1 day of data
Aha. Okay. Next question for you: Why did you say that your LDF contained all the transactions since the full backup?
May
10
comment Have full SQL Server restore but losing 1 day of data
Assuming you have a corrupt page, what kind of page is corrupt? If you don't know, use DBCC PAGE to see.
May
10
comment Have full SQL Server restore but losing 1 day of data
Wait though. Do you still have your database in some (albeit corrupt) form?
May
10
comment Have full SQL Server restore but losing 1 day of data
If you're in SIMPLE, the LDF is no use to you, because it would have been truncated every few moments.
May
10
comment Have full SQL Server restore but losing 1 day of data
Ok. In SIMPLE the only thing you can go back to is the last database backup. The log is no use. Let's talk about what you do have... For starters, what makes you say your database is corrupt?
May
10
answered Have full SQL Server restore but losing 1 day of data
May
9
answered Order by query optimization for multi select data (enum)