Viewing 15 posts - 8,176 through 8,190 (of 22,224 total)
OK. Sounds fine. But, you still don't know why the log was that big. Maybe there are load processes or something that require that level of log space. You may...
"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
May 13, 2014 at 7:09 am
ashok84.kr (5/13/2014)
"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
May 13, 2014 at 7:06 am
You can just run the shrink operation on the file.
But, the bigger question is, what caused the log to get so big? Was it a one-time event that's not...
"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
May 13, 2014 at 6:24 am
Excellent point on the storage of the cluster key in nonclustered indexes Ed. I completely missed that one.
"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
May 13, 2014 at 6:08 am
Again, because I can't see the behavior of your queries, I don't know.
A view doesn't do anything but store the query. It won't help performance at all unless you're talking...
"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
May 13, 2014 at 6:03 am
The ANSI connection settings can be changed by the connecting application. That's where I'd focus.
"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
May 13, 2014 at 6:01 am
And if that index is needed by the queries, while it's gone you'll see table scans instead of index access, so that impact could be substantial.
"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
May 13, 2014 at 6:00 am
It depends. A common practice for large data loads is to drop the indexes because they're not used during inserts and then recreate them after the inserts are complete. In...
"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
May 13, 2014 at 5:59 am
Well, a lot of the information is right there in the SQL Server documentation. A GUID is 16 bytes while a bigint is 8 bytes. That alone affects the distribution...
"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
May 13, 2014 at 5:56 am
In theory, the estimated values are a measure of the resources needed to execute a query. But they're just mathematical constructs with no actual relation to reality. Further, those constructs...
"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
May 13, 2014 at 5:42 am
OK. I think I somewhat understand now. The thing is, you're going to NULL values, you have to. You have a mismatched set of rows across the tables, so some...
"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
May 13, 2014 at 4:35 am
Never tried that. I'd just uninstall and reinstall. Safer that way.
"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
May 12, 2014 at 4:09 pm
So, I'm unclear how your tables map together. What are the primary and foreign keys that define the relationships. That ought to drive us towards a meaningful query. As it...
"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
May 12, 2014 at 4:08 pm
Stefan Krzywicki (5/12/2014)
Ed Wagner (5/12/2014)
Stefan Krzywicki (5/12/2014)
TomThomson (5/12/2014)
Ed Wagner (5/12/2014)
Sean Lange (5/12/2014)
Lynn Pettis (5/12/2014)
Sean Lange (5/12/2014)
Ed Wagner (5/12/2014)
"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
May 12, 2014 at 3:04 pm
Didn't the query show you what was in the memory? It came from somewhere on the system within your SQL server instance. Maybe it's just all index maintenance scripts 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
May 12, 2014 at 10:15 am
Viewing 15 posts - 8,176 through 8,190 (of 22,224 total)