Heh... I'm still trying to figure out why anyone would try to cache a 54 million row table...

Step 1, I would think, is to hunt down the vendor that provides you with the information... and then yank their tonsils out through their nose. Wow! They...

You're welcome... thank you for the feedback.

You're welcome and thank you for the feedback.

I haven't check all the code, but I see that you have a RETURN that I commented out in red...

Heh... use the heat of compression to make hot water, the thermal losses of expansion to provide refrigeration, and the left over pressure to drive a low pressure turbine.

Ken,

Yeah, you're right... go breaks the stride of variables... AQT won't handle it. Still not sure why you need the "GO"'s. Yeah, they force an early display but...

Ummm... my mistake, I think... you're probably taking about the "WINDOWS" server System Admin, huh?

That might be a different story but, still, I'd be inclined to let the DBA in....

If you dunno, you may be in trouble...

Who's going to set the files sizes? Who's going to do the load balancing for TempDB and other databases? Who's going...

Heh... If you're going to copy code 100%, the least you could do is put my name on it 😉

First, why are you using this as a proc... why...

Lowell, as always, brings up some excellent points and I, too, hate these types of sequence tables. They're a real pain and if the code isn't written perfectly, you...

The best thing to do would be for your organization to hucker down and fix the poorly written code by turning them into viable stored procedures or views.

Than notwithstanding, what's...

You must use Dynamic SQL to do such a thing...

CREATE PROCEDURE [dbo].[sp_vcGetStop]

@CheckTable varchar(15),

@Sequence numeric(10,0)

AS

EXEC ('SELECT CUID As Rt, WorkType FROM ' + @CheckTable + ' WHERE Sequence = '...

There is a registry setting that prevents SQL Server from being able to use OpenRowSet... look in the registry for "DisallowAdhocAccess" and change it's value to zero.

Also, OpenRowSet creates temporary...

I agree with Steve, but the code is so simple I wouldn't make a stored procedure or function for it... too much overhead for such a simple thing.