Same here. Can you generate execution plans for the two queries? Estimated of course since you don't want to wait for 10+ minutes again.

Generally, don't use them. Ever. Yes, there are exceptions to that rule, but you need to be extremely careful when deciding you have an exception. You may not actually have...

Nope. GO is an external construct for scripting within SSMS, not an actual part of TSQL as such. How about COMMIT TRAN?

Oooh! I may have to try that just to see what happens. I'll bet you looked great on that one. But here's a question, how long did it take you...

OK. Jack's explanation is more clear. Go with that one.

GO acts to close off open transactions.

Thanks! I've been practicing.

Whatever the DTS package is doing, the transaction is so large that it's filling the log file. Break the transaction down into more discrete parts so that you get...

First, you've got one index that's completely a waste (there may be more). Index 11 eliminates the need for index 7 because they both have the same leading edge. So...

Queries submitted to SQL Server go through a process called the optimizer. It makes decisions based on the data in the database as to what order to do certain processing...

No, each one is executed serially. Maybe the first one is holding a transaction open?

Much better query. But this part:

AND ds.LINK_ID NOT IN (Select LINK_ID from Demography_Summary where PRAC_ID IS NULL)

Again could be written as an OUTER JOIN. That's possibly your issue right there....

Not knowing your structure I can't rewrite the query myself, but I suspect the issue is you've got a join that's preventing you from eleminating the NULL values. Instead of...

Are you able to select data from the tables in SQL Server using Management Studio? If so, the error is on the Sybase side.

Here's a pretty basic intro to Try/Catch[/url].