Viewing 15 posts - 15,301 through 15,315 (of 22,219 total)
Depending on the data types, of course a few million records could produce a difference of 20gb. Actually, the data types involved must be quite small for several million records...
"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
April 28, 2010 at 7:13 am
d.srikanth50 (4/28/2010)
on monday to saturday at 3:30a.m.i have to schedule diferential backups also on everyday.
please guys let me...
"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
April 28, 2010 at 7:10 am
Will do. I was being lazy with the link and got caught. Sorry :crying:
"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
April 28, 2010 at 6:59 am
Although, again, I'd suggest a quick query against sys.dm_exec_query_stats. Order by physical/logical reads or physical/logical writes and you'll see the queries currently in cache that are hitting the system hard...
"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
April 28, 2010 at 6:57 am
Ninja's_RGR'us (4/28/2010)
Assuming this job has already run succesfully in the past :
1 - Either the permissions changed (NTSF or sql login)
2 - You're out of space on...
"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
April 28, 2010 at 6:53 am
GilaMonster (4/28/2010)
p.s. In SQL 2005, you cannot force an index seek. You can force an index to be used but you have no control over how it will...
"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
April 28, 2010 at 6:47 am
The fact is that data is neither stored nor retreived in precise order. Without the ORDER BY, that I'm not telling you to use, you have no guarantee how the...
"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
April 28, 2010 at 6:44 am
Have you run consistency checks on the databases? I'd be quite concerned about that. Also, you could try DBCC UPDATEUSAGE. I don't think it'll help, but it's the first thing...
"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
April 28, 2010 at 6:42 am
On a side note, foreign keys are for data integrity. They have little effect on performance. It's indexes that you need to look at to really alter performance.
"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
April 28, 2010 at 6:37 am
I can't tell you specifically why truncate is allowed and not delete when you give the alter permission, but you're wrong about rollbacks. Truncate can be rolled back.
"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
April 28, 2010 at 6:36 am
Applying hints is absolutely the last step in any tuning process. All you're doing is forcing the processor to only use that index for access, but because of the rest...
"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
April 28, 2010 at 6:34 am
The buffer pool is basically all remaining memory. You can't really manage it at all beyond setting the min & max values. Other than that, you manage how data 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
April 28, 2010 at 6:26 am
I don't entirely understand the issue. Are you saying that you're running perfmon across the network to collect data? Generally, this is not an approach I use. Instead, I'll run...
"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
April 28, 2010 at 6:20 am
Yes, but...
NOLOCK hints can cause you to get erroneous data. Not only will you see columns that have been changed but not yet committed within a transaction, but you can...
"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
April 28, 2010 at 6:16 am
People here may not have, or may not want, StackOverflow logins to answer your question. If you want an answer here, ask the question here. Otherwise, wait patiently over there.
"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
April 28, 2010 at 6:14 am
Viewing 15 posts - 15,301 through 15,315 (of 22,219 total)