Viewing 15 posts - 4,366 through 4,380 (of 22,219 total)
On the PK:
Don't confuse the primary key and the clustered index. While the default is for the PK to be clustered, you don't have to make the clustered index 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
September 29, 2016 at 5:47 am
BLOB_EATER (9/29/2016)
"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
September 29, 2016 at 5:31 am
drew.allen (9/28/2016)
mcfarlandparkway (9/28/2016)
This is what...
"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
September 28, 2016 at 3:42 pm
ScottPletcher (9/28/2016)
Eric M Russell (9/28/2016)
ScottPletcher (9/28/2016)
"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
September 28, 2016 at 3:40 pm
mw112009 (9/28/2016)
--This gives you the list of all the SSRS reports in your Reporting Server. Agree ?
-- I am looking forqward 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
September 28, 2016 at 12:53 pm
For production, first thing, everyone has a second login from their standard one. One that's for your machine, email, development, whatever. Another that's only for production. A lot fewer errors...
"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
September 28, 2016 at 11:57 am
Anyone who has the capacity to overwrite the database in a restore from a security stand point is going to be able to undo your changes. DDL triggers don't have...
"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
September 28, 2016 at 11:48 am
I don't completely understand what you're asking? Can you expand on what it is that you expect to return? What's the data structure you're pulling information from?
"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
September 28, 2016 at 11:43 am
There's no way logically that can work because you would be joining all three columns on all three columns. The syntax doesn't support it and the language doesn't either.
Can you...
"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
September 28, 2016 at 11:42 am
You would have to poll all the tables in the database, one-by-one, to determine if there are changes. That's a poor approach. You could read the log using DBCC LOG...
"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
September 28, 2016 at 11:39 am
Going to a heap in the hopes that you get improved compression is not the way to tune queries. If that clustered index is in use, it needs to stay...
"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
September 28, 2016 at 11:32 am
A view doesn't have statistics.
A materialized view does, because a materialized view is an index. You can't drop statistics from an index.
"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
September 28, 2016 at 7:16 am
I think I'd add another table in there. Instead of having a direct link between ProductPropertyType and ProductPropertyValue, I would define the values, the properties, and then have a table...
"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
September 28, 2016 at 7:14 am
Eric M Russell (9/27/2016)
Talib123 (9/27/2016)
I'm a production DBA and have been for a good while.
I can query, join filters but how do I get my T-sql skills 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
September 27, 2016 at 8:54 pm
There has to be something else causing the issue. If you're seeing different execution plans, it's because the mechanisms used to generate those plans have different inputs.
"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
September 27, 2016 at 8:52 pm
Viewing 15 posts - 4,366 through 4,380 (of 22,219 total)