Use Variables. instead of DTS. when using variables in the Script Component.

Have a look at this Books Online topic too: Comparing the Script Component and the Script Task.

Have you identified what query is run on the server when the client timeout occurs? Adding the Attention eventclass to a profiler trace can help with that.

This blog entry...

Keep in mind those reports are only available if Service Pack 2 is installed.

Here's one simple way to do that. Just copy-and-paste the results into another query window.

USE MyDatabase

SELECT 'SELECT COUNT(*), ''' + name + ''' FROM ' + name FROM sys.tables

Or...

You're welcome. Thanks for posting back what you found.

SQL Server 2005 Books Online

---

The SPID value of '-2' is set aside as an indicator of connectionless, or orphaned, transactions. SQL Server...

Test environments are typically open to doing things like that without having negative consequences. Only you can decide that though.

If it's shared environment you might want to talk to...

One by one.

Since it's a test environment you might want to track back to the cause.

If you're using the Script Task in SSIS you would use VB.NET instead of VBScript. The steps are about the same as the script you posted though, just different...

Denise,

Is this a continuation of this post? http://www.sqlservercentral.com/Forums/Topic481065-146-1.aspx

Did you try using the UOW ID that was previously suggested and it didn't work?

You should be able to find tools and articles to help answer that question at this site:http://www.wireshark.org/. Look for some of the articles and webcasts by Laura Chappell.

I've seen this type of solution in a few posts around here also, providing this is SQL 2005.

SELECT DISTINCT Name, ID, Dept,mylist

FROM myTable t1

CROSS APPLY

(SELECT CONVERT(VARCHAR(10),Code) + ',' AS...

Here's a relatively straightforward way of doing that.

1. In IIS configure a virtual directory that points to the location of the .JPG files.

2. In SQL, store the relative path...

Michael Earl (4/7/2008)

---

By the looks of the application and user name from sp_who2, you are the problem.

You have management studio open with an open transaction locking the table you are...

To kill a MSDTC transaction use the Unit of Work ID with the KILL command.

USE master

SELECT req_transactionUOW

FROM syslockinfo

WHERE req_transactionUOW <> CONVERT(UNIQUEIDENTIFIER,0x0)

KILL 'UOW value'

Reference:

BOL: KILL (Transact-SQL)

Could be that you're being blocked by another process. In SSMS open up the Activity Monitor under Management. Look at the Blocked and Blocked By columns.