Viewing 15 posts - 6,556 through 6,570 (of 22,226 total)
Phil Parkin (3/24/2015)
Actual rows and Est rows are very different. Are your statistics up to date?
Yeah, estimated 1, actual 87000, that's a slight disparity. No wonder it assumed a scan...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 24, 2015 at 5:47 am
Please post at least the execution plan so we can see how the optimizer is resolving the query based on your structures.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 24, 2015 at 4:15 am
The easiest way is going to be to run the RESTORE using WITH MOVE. But, that means the file layout has to be the same, even if the locations are...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 24, 2015 at 4:14 am
It's stored as a clustered index, so there is data stored within the database.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 23, 2015 at 7:31 am
GilaMonster (3/18/2015)
Luis Cazares (3/17/2015)
Can someone help with a crystal ball or interrogation system for this thread?http://www.sqlservercentral.com/Forums/Topic1668185-391-1.aspx
Sorry, mine's broken, it's only showing clouds.
OMG! That explains why I've been doing all this...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 18, 2015 at 7:21 am
Like I said, you probably won't be able to shrink immediately. The unused log space and closed transactions are before the open transactions. Until that changes, you're going to need...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 18, 2015 at 7:19 am
I think the issue must lie somewhere besides the cardinality estimator. In fact, both plans have the exact same estimates. They even have the exact same costs. Something else is...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 18, 2015 at 7:18 am
Like I said, capture the wait statistics that occur during the process. That will tell you what's running slow. You'll have to figure out why.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 18, 2015 at 7:10 am
Look to the row estimates. I'm sure that's probably the issue. The 2014 cardinality estimator is new and if you're seeing differences in execution times, it could be because of...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 17, 2015 at 7:10 am
PHYData DBA (3/16/2015)
However I have never read anything that made me think of Star Wars II so much.
You know...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 16, 2015 at 11:03 pm
Maybe it's using the IP address. Try that. In general, you won't use the database name to connect from Management Studio. Just the server name. It's also possible you're AD...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 16, 2015 at 10:49 pm
The log backup just reclaims the space for committed transactions within the log. It doesn't affect the size of the log at all. If you do need to reduce that...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 16, 2015 at 10:44 pm
Dan121 (3/16/2015)
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 16, 2015 at 1:22 pm
dan-572483 (3/16/2015)
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 16, 2015 at 11:06 am
Without seeing the queries involved, I'm just guessing.
But, it is possible that eve if it's just getting scanned, it's still useful. Let's say your clustered index consists of 1000 pages...
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
March 16, 2015 at 10:45 am
Viewing 15 posts - 6,556 through 6,570 (of 22,226 total)