Viewing 15 posts - 14,956 through 14,970 (of 22,219 total)
I'd suggest getting a copy of the book "Microsoft SQL Server 2008 Internals" by Kalen Delaney. This is a huge topic, as was already noted, and just can't possibly be...
"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 24, 2010 at 8:25 am
Just adding another thought...
Most app developers that need to support multiple platforms are taking advantage of ORM tools like Hibernate, nHibernate, LINQ, Entity Framework, etc., to perform the work for...
"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 24, 2010 at 7:51 am
I'm with Paul, obviously it would be better to have multiple machines, but if you can't, multiple instances will at least simulate the results. This way you avoid the issue...
"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 24, 2010 at 6:16 am
Even though both operators have the word SCAN in them, there is no real comparison between a Constant Scan and an Index/Cluster/Table Scan.
Usually, but not always, an Index/Cluster/Table Scan 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
May 24, 2010 at 6:14 am
It really depends on the situation, but for most of us, no, this is a waste of time & effort. I've been working for a company for almost nine years....
"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 24, 2010 at 6:04 am
The best way to deal with sudden issues on the database is to prepare beforehand. Know how to look for contention. Know how to look at the processses that 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
May 24, 2010 at 6:00 am
I've honestly never tried it that way, so I'm not sure where to go. If you know which procedure is giving your problems, I just work with it on my...
"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 21, 2010 at 4:36 am
Traditionally it's considered bad form to hijack someone elses question. Also, when you do this, the only people that are aware of the new question are those that are already...
"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 20, 2010 at 10:59 am
It really depends on what the error is. Not all errors cause a loss of connection, so you'll still see the RPC or Batch completion event.
Profiler isn't necessarily the place...
"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 20, 2010 at 10:51 am
You can make the data file any size you want, but then it will consist mostly of free space. Right click the database and check the properties. That's an easy...
"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 20, 2010 at 8:54 am
NOLOCK is what is known as dirty reads. It prevents shared locks from being placed on data. This can speed up access. BUT, it also means that you can get...
"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 20, 2010 at 8:52 am
If the calculation is really simple, say adding two columns, then no, storing it doesn't really make sense, but if the calculation is complicated, then it makes more sense to...
"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 20, 2010 at 8:48 am
rafael_si (5/20/2010)
"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 20, 2010 at 7:50 am
mtassin (5/20/2010)
Grant Fritchey (5/20/2010)
I'm sorry to disagree with you here, but dynamic queries do get cached. And if you build them using the parameterized approach, they can get reused too....
"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 20, 2010 at 7:34 am
It depends on the query and your goal. SCHEMA_BINDING and indexed views are different critters. An indexed view is, effectively, a second table because the query that defines it 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
May 20, 2010 at 7:31 am
Viewing 15 posts - 14,956 through 14,970 (of 22,219 total)