I thnk that you just need to extend your derived table and join it :

SELECT s.Record_Count,

t.Trip_ID,

s.Compart_No,

...

Remember that the ADO connection object has a timeout property that is completely separate from the SQL Server timeout property. Both need to be set appropriately.

The following brings up the standard Windows connection dialog and returns a Connection object (You need Microsoft OLEDB Service Component and Microsoft ActiveX data Objects in your project references) :

...

You could set up a trigger to output details to a table of whose process is running although not the specific stored procedure or application. The following from BOL...

Good thinking. You're quite right. Many thanks.

Good point about time - careless of me. If this is a concern, you need :

WHERE StartDate < DATEADD(d, DATEDIFF(d, 0, DATEADD(d, 1 - DAY(GETDATE()), GETDATE())), 0)

This calculates the...

Neater, and probably faster, would be :

WHERE StartDate <= DATEADD(d, -DAY(GETDATE()), GETDATE())

Not appropriate in this sceanrio, but thanks for the suggestion - it certainly could be an option in other cases.

That looks interesting - I'll give it a try. Thanks for the help.

Thanks. Unfortunately, I forgot to mention that the SPs are big. I think executesql is limited to 8K which will not be enough.

Thanks, anyway.

Good question! Not my design.

Good ideas. Unfortunately, it is using SQL security and the application's security creates user ids 'on the fly' and throws them away when the user logs out. I...

My approach is to use 100% only if its static data or I konw that I am only ever adding records to the end (eg clustered on an identity field)....

Perhaps the only solution to meet the spec will be to use SQL Server as an indexing engine but hold all the sensitive data in a separate .dat file that...

It would seem to me that the only way to guarantee that data genuinely is deleted immediately is to overwrite it with garbage. The problem comes down...