(R)elational (D)atabase (M)anagement (S)ystem.  R = relational, without it = flat files.

However, nowadays RDBMS is equal to DBMS to most non-techs....

Brian,

You are correct!  I forgot

You are correct you cannot use GETDATE() inside a UDF.  However, you CAN pass it as a parameter.  udf_GETDATE(@Today) where @Today was SET = to GETDATE()

Sounds like permissions alright.  Research sp_addlinkedsrvlogin to add credentials for who the linked server should connect as...

I guess the real question is....

WHY are you allowing DEVELOPMENT to run PROFILER (which if done incorrectly can bring your server to a halt) on PRODUCTION (Assumption)?????

I would want to...

I would change to use NOT EXISTS (less expensive).

To know which table this was not found in 1 way is to:

Have a bit column per all of the misc tables...

Sounds like a WINS\DNS problem.  Get with the engineers that rebuilt the servers to make sure that the names are properly configured in the PDCs and Active Directory, WINS server,...

These are created under "User Defined Functions".  They are used in conjunction with stored procedures/ad-hoc queries and are referenced by owner.UDFname.

i.e SELECT dbo.udf_HelloWorld

Look up UDF or user defined functions here...

pretty much nothing.  A composite (or covered/covering) PRIMARY KEY IS a UNIQUE INDEX.  The key is the CLUSTER which will re-arrange your data physically.

PLEASE NOTE:  Don't forget to include FILL...

Have you tried ORDER BY ColumnX?  If YES and that failed you may need to apply an ORDER BY type INTEGER column and then use that for ordering purposes only.....

2 cents worth....  Don't order by ORDINAL position it may/may not come back and bite you.  Instead ORDER BY [ID], SQL will use the "derived" value for the ordering....

Right before the semi-colon there is an extra parentheses.. ??

How 'bout something like UPDATE tableA SET ColB = REPLICATE('*', 12) + RIGHT(RTRIM(LTRIM(ColA)), 4)

A.  no.  If there is no point to do it, don't

B.  If creating a PK of 4 - 5 columns does that to you why not create a CLUSTERED UNIQUE...

IF Deleted is a BIT field it can ONLY be 0 or 1 and NOT 0,1 ?