Hi, sorry for some reason my last post didn't go through.

Yeah, it's running a begin tran, commit tran and also the followign select before the update

Select dbo.AutoNumberSettings.* From dbo.AutoNumberSettings...

You don't think the I/O throughput on the db server could cause a bottleneck on the app server do you?

I am not seeing any network queuing or disk queueing on...

Hi Gail,

I am not aware that I can change that? If so, I'm all ears...

My options are to tune the server, tune the hardware, and or tune the indexes.

I have a small concern that the hyperthreading on the db server processors may be...

Sorry, i've attached it 🙂

Thanks Gail and Ninja!

LOL

Here's the table, it's name is not really what it looks like, unfortunately I have little say in the structure of this db as it is vendor-created.

[dbo].[AUTONUMBERSETTINGS](

[CLASSNAME] [nvarchar](250)...

Hi, and thanks for the quick response!

FYI - I removed our server name, user name, and database name from the graph.

As you can see the web service issues the same...

You could also pull this data from dmv's and write it to a table using a job.

Here's a helpful query:

SELECT session_id, connect_time, last_read, last_write, TEXT

FROM sys.dm_exec_connections

CROSS APPLY sys.dm_exec_sql_text(most_recent_sql_handle) AS ST...

LOL - I will call India and tell them!

Thanks much 🙂

Yeah, I am beginning to think it's really not doing anything either 🙁

What a bummer when your app is 3rd party and they don't dispose correctly! I have a slick...

I thought the keep alive interval (SQL 2005) meant that SQL Server would check the connections according to the interval set (I have it at 7200000). If the connection does...

I've not had any negative effects related to this message when it comes directly after a dbcc checkdb commandso id say no its an expected behavior.

The script has now been updated with the correction.

Thanks!

Hi, it looks like something happened when the script was posted, here it is again in full:

EXEC sp_MSforeachdb @command1='USE ?

DECLARE @Roles varchar(200)

SET @Roles = ''db_datareader, Init_Role, Viewer''

DECLARE @sqlcmd1 nvarchar(100)

CREATE...

Ok, got it here,

SQL Browser runs under UDP port 1434 not TCP port. telnet doesn't work with UDP because there is no acknowledgement from UDP protocol.

So.. how I figured out...