I'm sorry, I don't understand what you're asking.

Do you mean, where are the stored procedures? Depending on the app, there may not be any, but if there are, they're part...

Unless you put a lock on the table as suggested in the previous post, yeah, the second query will try to delete what the first query was doing.

You may want...

Derek Karpinski (10/18/2007)

---

Nolock - depends on your db. But can be useful, if you are careful to only use it on SELECts.

Where you don't need absolute acuracy. For...

Sounds reasonable. I guess I'm going to have to get off my dead behind & get my MCDBA.

Seriously though, it doesn't sound unreasonable. You just need to get the infrastructure...

Exactly.

Another option might be to keep them in the call app and pass them in as either a delimited list or XML list and then either turn the delimited list...

Well, it depends. Most of the time, yes, but watch for Table Spool operators in the query plan as a way to spot interim tables being built. You'll definitely see...

If you read Itzik Ben-Gan's book on SQL Querying, he lumps CTE's and derived tables together because they are so similar in behavior (as you're seeing in the execution plans...

What the hell, I'm just a volunteer at PASS, so the pay cut when I get fired isn't going to be too bad.

I think a lot of these are very...

I understand there's no server.

If you built FoxPro app and had a shared database that more than one user was going to hit, each of the clients had some...

Sure sounds like a client type of error. We get the same thing when we try to connect to Oracle when the Oracle client hasn't been installed on the server...

Here you go. This is using AdventureWorks. Have fun:

CREATE VIEW y

AS

WITH x AS (SELECT *

FROM [HumanResources].[Employee]

)

SELECT * FROM x

GO

SELECT * FROM y

Please tell me that 260 tables were designed with a clustered index as part of the design.

If you left the clustered index off all the tables as you built the...

Definitely BOL as stated above.

Additionally, you can check this article by Robyn Page[/url]

You can't trap errors in 2000. TRY/CATCH was introduced in 2005 in order to provide error trapping.

I apologize, but I've never heard of the nested update statement before. I ran it through Google and BOL. I'm not seeing it anywhere.