Viewing 15 posts - 22,816 through 22,830 (of 49,552 total)
No, just the last full. So with full1, diff1a, diff1b, full2, diff2a, diff2b, you'd restore full2 then diff2b. You can't restore full1 then either of the diff2 as full backups...
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
October 21, 2011 at 12:23 pm
The vendor doesn't have a frigging clue what they're talking about. I can run full, diff and log backups simultaneously, all will succeed. (the diff will wait until the full...
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
October 21, 2011 at 12:21 pm
They're in the default trace, so you can use that with no extra work required.
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
October 21, 2011 at 11:59 am
I just took a quick look, but to be blunt that procedure probably needs a rewrite.
Permanent tables instead of temp tables? That's gonna cause all osrts of fun if...
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
October 21, 2011 at 11:48 am
Oh, so the log file exists, but it's from another database (or something's been badly mangled in it.)
At this point it's pretty much restore from backup or hope a repair...
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
October 21, 2011 at 11:02 am
dva2007 (10/21/2011)
My impression is we can have clustered index on service_id as it is unique for each row
Clustered indexes don't have to be unique. It's generally recommended that unique...
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
October 21, 2011 at 10:26 am
If the drive is damaged you're probably restoring from backup.
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
October 21, 2011 at 10:25 am
How about you give us the entire query? Can't work on drips and drabs. Also execution plan, table and index definitions. http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
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
October 21, 2011 at 10:24 am
6 minutes to retrieve, sort and transmit 143 million rows doesn't sound too bad. That's a huge amount of data. What are you doing with 143 million rows?
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
October 21, 2011 at 9:56 am
Those 2 plans are, as far as I can tell, absolutely identical. Did they perform radically differently?
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
October 21, 2011 at 9:50 am
Elliott Whitlow (10/21/2011)
If the files have moved I don't see much of a choice..
Move them back where they should be and offline/online or ALTER DATABASE ... MOVE then offline/online. Or...
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
October 21, 2011 at 9:35 am
Without seeing at least the procedure and preferably the execution plans too, no.
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
October 21, 2011 at 9:30 am
Loner (10/21/2011)
I usedselect *
from @table
INNER JOIN table1
INNER JOIN table2
WHERE...
That's just about guaranteed to produce a sub-optimal execution plan. One of the senior devs on the Query Optimiser team explicitly states...
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
October 21, 2011 at 9:26 am
Loner (10/21/2011)
Is there any way to determine what the problem is?How do I find out if it is parameter sniffing?
GilaMonster (10/21/2011)
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
October 21, 2011 at 9:11 am
Table variables and large amounts of data? Hell yes that's a problem unless all you're doing is a direct select from the table variable, no joins, no filters.
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
October 21, 2011 at 9:10 am
Viewing 15 posts - 22,816 through 22,830 (of 49,552 total)