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.

System catalog view:

SELECT * FROM sys.servers

It's one of the properties, is_rpc_out_enabled.

Look up the EXECUTE statement in BOL:

EXECUTE ('USE STUFF;DROP INDEX OWNER_idx ON dbo.OWNER')

AT SQLnk

The linked server has to support RPC calls:

EXEC master.dbo.sp_serveroption @server=N'SQLnk', @optname=N'rpc', @optvalue=N'true'

Oh, and, Warren Peace: SKY HIGH...

You can use IS_MEMBER() to determine the current users inclusion in a particular group. There are also a series of dynamic management views (DMV) that access security. Try sys.database_role_members and...

I'd heard C++ too. I don't recall the source though.

The error logs are just text files. You should be able to simply open them in a text editor, completely seperate from SSMS.