Scalar UDF's in SQL Server are pretty much like cursors. They process row-by-row, which can be performance killers on larger tables.

No chance! That syntax is simply not supported.

I guess your best bet is to read this in "Inside SQL Server". Or just google on this. It would be a very long explanation here.

Well, I'd say the 33 in the first example is also "correct". When you read up on data type precedences in BOL you'll find it there explained.

Also, for the lazycoder...

Sorry, no real answer from me, but http://www.sqldts.com is a very oftern referenced site for DTS-related questions. Maybe you find something there.

Maybe this will help in addition to what Wes already said:

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ansvcspg.mspx

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/anservog.mspx

http://support.microsoft.com/default.aspx?scid=kb;en-us;838622

Are you running multiple instances on that server?

Select 100/3 

-----------

33

(1 row(s) affected)

and yes, it's because both operands are interpreted as integer, thus the result is also an integer. But why don't you try this yourself in...

Hey, Brian, why should you complain anyway? I like the article, too.

And I'd rather read a good article twice or more than a...

Sorry, no answer since I don't use replication, but don't you think one thread instead of four would be enough?

Do a search on my site for Windows XP. Returns 18 links to MS knowledgebase. Too much to post here.

While the most efficient way is to do this at the client, SQL Server MVP Adam Machanic has posted some nice example here:

http://sqljunkies.com/WebLog/amachanic/archive/2004/11/10/5065.aspx?Pending=true

Would EXEC sp_helpdb 'your db name goes here' be a start? Or in case when you prefer EM, setting the view option to taskpad?

Yes, you really need to read the article I've reference. In the meantime what about?

SET NOCOUNT ON

SELECT

 TOP 256 Number = IDENTITY(INT)

INTO

 MyNumbers

FROM

 Sysobjects S1

CROSS JOIN

 Sysobjects S2...

This might also be interesting:

http://www.sqlservercentral.com/columnists/jtravis/understandingthedifferencebetweenisnull.asp