Viewing 15 posts - 7,996 through 8,010 (of 22,226 total)
A WHILE loop? No, I haven't done that sort of testing at all. It's not something I'd write within T-SQL or expect to perform well, natively compiled or not.
"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
June 13, 2014 at 3:50 am
Suresh Arumugam (6/12/2014)
SO, do you mean that even if there are 500 tables in Sybase, we need to manually add source and destination data flow...
"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
June 13, 2014 at 3:48 am
Dave62 (6/12/2014)
OCTom (6/12/2014)
...Any bickering between developers and DBAs is childish and is counter-productive to the goal of delivering quality.
Tom
BUT THEY STARTED IT!!!
:hehe:
Winner of the Internet this morning. Well done!
"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
June 12, 2014 at 7:20 am
IT researcher (6/12/2014)
GilaMonster (6/12/2014)
IT researcher (6/12/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
June 12, 2014 at 7:19 am
IT researcher (6/12/2014)
Why?
SQL instances don't need to be rebooted daily. Hell, I know of instances that have been running over 6 months.
The SQL server instance is used by...
"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
June 12, 2014 at 7:02 am
GilaMonster (6/12/2014)
IT researcher (6/12/2014)
The sql server starts everyday at 8:30 AM and stops around 9:30 PM.
Why?
SQL instances don't need to be rebooted daily. Hell, I know of instances...
"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
June 12, 2014 at 6:47 am
OCTom (6/12/2014)
Any bickering between developers and DBAs is childish and is counter-productive to the goal of delivering quality.Tom
THIS!
"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
June 12, 2014 at 6:43 am
Wait stats tell you what the server is waiting on. But, you can't know if you have a performance problem by only looking at cumulative wait times, even though you're...
"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
June 12, 2014 at 6:42 am
IT researcher (6/12/2014)
SQL server restarts every night. Does these values reset on restart?
Yes, it's since a restart. So this is cumulative since that restart. But, normal can only 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
June 12, 2014 at 6:12 am
GilaMonster (6/12/2014)
IT researcher (6/12/2014)
SQL server restarts every night. Does these values reset on restart?
wait times are cumulative since SQL started
For a change I'm going to disagree with Grant. Daily...
"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
June 12, 2014 at 6:08 am
Without seeing the query plan, the structures, the query... nope, not really.
My tests show a pretty consistent faster behavior for the natively compiled procedures.
"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
June 12, 2014 at 5:29 am
The very best wait times are zero.
But, that's not going to happen, so you need to know how your waits are changing over time to determine if there are issues....
"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
June 12, 2014 at 5:27 am
[/url]
And, I'm with Gail, turn off auto shrink.
"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
June 12, 2014 at 3:46 am
The Import/Export wizard can work, but if you hit issues where you need to manually intervene it can be a pain. I'd say the best bet would be to build...
"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
June 12, 2014 at 3:43 am
I'd go with the DENY approach and then make sure that only appropriate people have access to the system.
However, that's not even the scary thing. The scary thing is when...
"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
June 12, 2014 at 3:41 am
Viewing 15 posts - 7,996 through 8,010 (of 22,226 total)