Viewing 15 posts - 16,021 through 16,035 (of 22,219 total)
This is more or less a paging problem. There are a number of possible solutions:
http://www.sqlservercentral.com/articles/66030/%5B/url%5D
http://www.sqlservercentral.com/scripts/31280/%5B/url%5D
These are just the first couple that I came across after searching on the site. 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
December 16, 2009 at 9:37 am
Everything else is absolutely equal, identical databases, identical indexes on the databases, identical statistics on the indexes, identical queries, identical parameters... I've moved databases between servers before without the execution...
"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
December 16, 2009 at 9:33 am
The only way you can do this is if you've set up some auditing method prior to the deletes occurring or if you've got a trace running that captured 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
December 16, 2009 at 9:27 am
I'm sorry, I'm not there, so I can only answer based on the information you've provided.
From what you've said, a long running process was reading some large piece of data....
"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
December 16, 2009 at 9:24 am
The Dixie Flatline (12/16/2009)
I have a question about penance, Grant:Can I repent if I'm not certain I have ever pented in the first place?
You're asking 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
December 16, 2009 at 9:20 am
It really depends on what you're doing with SQL Server. Let's say you implement the hierarchy data type. VS 2005 won't be able to consume it. But if you keep...
"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
December 16, 2009 at 9:10 am
Then use a derived table and join against it. That would, more or less, be the equivalent of maintaining one WHERE clause and then using it for sub-selects.
"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
December 16, 2009 at 9:06 am
Compression is only available for Enterprise.
Cool stuff though.
"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
December 16, 2009 at 9:02 am
Grant Fritchey (12/16/2009)
From what I can see this person has tried to demonstrate some work, but good googly moogly, who is going to read all that stuff & eval 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
December 16, 2009 at 8:59 am
What about something like this?
SELECT
a.provcode
,COUNT(DISTINCT acctno) AS 'Patient...
"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
December 16, 2009 at 8:53 am
I agree with Steve & Lynn, I'm confused.
Based only on what you've said, I'd say the answer is no, you can't use the WHERE clause of the outer query within...
"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
December 16, 2009 at 8:49 am
In order to prevent a user from seeing only certain columns, you'll need to either limit the users access through a view or a stored procedure. If you give them...
"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
December 16, 2009 at 8:46 am
Two things come to mind, but I'm not sure either is applicable. It could be contention, other processes interfering with yours, although I would think you'd either see errors or...
"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
December 16, 2009 at 8:43 am
Whoa!
From what I can see this person has tried to demonstrate some work, but good googly moogly, who is going to read all that stuff & eval it? Anyone want...
"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
December 16, 2009 at 8:38 am
There is no way to hack in and retrieve the 'sa' password.
"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
December 16, 2009 at 8:34 am
Viewing 15 posts - 16,021 through 16,035 (of 22,219 total)