Viewing 15 posts - 8,296 through 8,310 (of 22,232 total)
1) DBA work is usually, by definition, 24/7. It's just the nature of the beast. We're frequently on call to handle emergencies. That said, most of the time, it's a...
"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 1, 2014 at 4:59 am
One argument against error handling in T-SQL is that there is already error handling in the calling application. To which I'll respond that there are unique error events within SQL...
"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 1, 2014 at 4:54 am
I'm not sure Grant Fritchey knows the answer to this. Is it a home-grown shipping process? I don't think the normal one flushes the cache.
"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 1, 2014 at 4:51 am
Luis Cazares (4/30/2014)
pooyan_pdm (4/30/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
April 30, 2014 at 4:36 pm
Tons of stuff has changed. First, did you change the compatibility level on your database to 120? If not, you're using the old statistics with the new optimizer in compatibility...
"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 30, 2014 at 12:36 pm
ErikMN (4/30/2014)
So to summarize:CONS:
- Slightly more complicated and slightly more costly to query
One table (denormalized):
PROS:
- Slightly faster queries
Careful. It's at least partly a myth that denormalized storage is faster. 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
April 30, 2014 at 11:09 am
shafirmubarak (4/30/2014)
Yes, the unique enforcement would be absolute necessary.But i was not sure how surrogate key will be of use?
In some situations it will help performance to have a...
"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 30, 2014 at 11:01 am
shafirmubarak (4/30/2014)
For example, user id is used as a linkage across multiple tables.
I am concerned about defining a key for the child tables as it requires 3- 9 columns...
"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 30, 2014 at 10:25 am
Instead of trying to capture the plan live, just get it from the plan cache using sys.dm_exec_query_plan. You can combine it with sys.dm_exec_sql_text to identify the specific code you're interested...
"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 30, 2014 at 10:24 am
Luis Cazares (4/30/2014)
Unless you're not doing log backups, the logs are constantly growing and no one cares about PIT recovery. Sounds nuts, but I've seen it.:hehe:
Until all performance stops because...
"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 30, 2014 at 10:21 am
If the other indexes were created for a reason and the code hasn't been modified, then the likely answer is that they're still needed. You can look at the usage...
"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 30, 2014 at 9:08 am
This is the third thread for the same problem.
Have you done any of the things I've suggested on the other two?
"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 30, 2014 at 8:52 am
There is a tiny impact on performance because you're using resources to backup the logs. But it's really tiny. If you're already at 99% resource usage, adding this might 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
April 30, 2014 at 8:51 am
Since you've posted this question to a second location, we're now getting into cross-chatter. I made several recommendations over there for how to fix it. It depends on your 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
April 30, 2014 at 7:47 am
Ha! In short, no, it doesn't "stay shrunk". As you add data (or junk mail) to the system, it's going to need to grow to contain that additional data. 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
April 30, 2014 at 7:43 am
Viewing 15 posts - 8,296 through 8,310 (of 22,232 total)