Viewing 15 posts - 17,866 through 17,880 (of 22,226 total)
As the last post showed, @@ServerName gets you the name of the server, DB_NAME() gets you the current database. If you pass it a database ID, it will get any...
"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
March 31, 2009 at 4:59 am
There's nothing all that special about a view. It's just a query that sort of behaves like it was a table. If you need to move data out of 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
March 31, 2009 at 4:53 am
The index is bigger. That means more disk space will be needed to maintain. It's possible that it will have more levels because of the extra size which will add...
"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
March 31, 2009 at 4:48 am
pandeharsh (3/31/2009)
Suppose i write a general proc like this.
Create proc Example
@empid int,
@Mode varchar (1),
@fname varchar (100),
@lname varchar(100)
As
If (@Mode='S'
Begin
Select fname,lname from emp where empid=@empid
End
If (@Mode='I'
Begin
Insert into...
"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
March 31, 2009 at 4:45 am
If the procedures are still in the cache you can query sys.dm_exec_query_stats to see exactly how long the procedure ran, how many resources it used, etc. You can even combine...
"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
March 31, 2009 at 4:37 am
You may need to filter the data. Include a WHERE clause to limit the amount of information you're getting back.
"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
March 31, 2009 at 4:35 am
I guess the question is, do you want grow your own monitors or do you want to go & purchase some of the more sophisticated monitors?
If you want to grow...
"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
March 31, 2009 at 4:33 am
That's all right.
Pick up a copy of SQL Express. It's free and you can learn most of what you need there. When you want to expand into mirroring and...
"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
March 31, 2009 at 4:20 am
iqtedar (3/30/2009)
"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
March 30, 2009 at 6:16 pm
Excellent. Thanks for letting us know it worked.
"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
March 30, 2009 at 6:10 pm
GilaMonster (3/30/2009)
Lynn Pettis (3/30/2009)
Just what do the users expect us to do???Read their minds, pull out a magic wand and make the nasty error go away, of course.
😉
You forgot quickly....
"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
March 30, 2009 at 5:59 pm
I agree with Paul. Do a FULL SCAN when you update the statistics.
"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
March 30, 2009 at 5:58 pm
Oh man, thousands... network connectivity, security, service shut down, changes to connection strings... Those are just the easy ones. It could be client configuration changes... It's really hard to say.
"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
March 30, 2009 at 1:28 pm
Actually I would have expected that to be a problem in 2000 as well. All 2000 is doing is an implicit convert, that you should get in 2005 as well....
"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
March 30, 2009 at 1:26 pm
Looks like you either have a connection error, or possibly your DTC process is down:
Microsoft.CommerceServer.Runtime.CommerceException: [highlight=#ffff11]Could not connect to datasource [/highlight]---> System.Runtime.InteropServices.COMException (0x8004D00A): [highlight=#ffff11]New transaction cannot enlist in the specified...
"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
March 30, 2009 at 1:17 pm
Viewing 15 posts - 17,866 through 17,880 (of 22,226 total)