Have a look here:

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

You might want to have a look at "Precision, Scale, and Length" in BOL. It contains a nice table:

I have a table of people, including birthdays, and I'd like to insert a record into a separate table when the person turns 18. In concept, what I'd like to...

Just use EXEC() instead. The difference is well explained here: http://www.sommarskog.se/dynamic_sql.html

But as your are using this for adminsitrative purposes only, both are equally good.

You might want to take a look at BOL for "CREATE FUNCTION". There's a nice example how to calculate the ISO week number.

A quick and dirty basic construct (untested) might be:

DECLARE @stmt NVARCHAR(200)

WHILE EXISTS

 (

 SELECT 

  * 

 FROM

  sysobjects

 WHERE  crdate> < your criteria >

 AND OBJECTPROPERTY(id,'IsUserTable')=1

&nbsp

BEGIN

 SELECT

 @stmt = 'DROP TABLE ' + name...

Forget it! Again, please read the link I've posted. The currently implemented DATETIME datatype *always* contains both, a date and a time portion. But the effects of this and the...

You might want to search here for xp_cmdshell and OSQL. Syntax is also explained in BOL. Sorry, I haven't got a working example at hand right now.

Just a quick script

declare @timeout varchar(10)

set @timeout = '12:00 am' --your data

select cast(@timeout as datetime)

set @timeout = '12:00:00' --slightly modified

select cast(@timeout as datetime)

------------------------------------------------------

1900-01-01 00:00:00.000

(1 row(s) affected)

------------------------------------------------------

1900-01-01...

You might want to read SQL Server's Online Help on both topics or search the fora here.

Unfortunately that requires that David gets his credibility back first. His boss needs to listen to him again and believe what he says. From my own observations that is no...

See, if this helps: http://www.karaszi.com/sqlserver/info_datetime.asp

It would also be helpful, if you could post typical input parameters for the stored procedure.

No, I'm afraid, but this is a known behaviour. It will only work up to 8,000 characters and is a well-known trick to flatten a table.

Watch out for this:...

Now that reminds me of http://mindprod.com/unmain.html 

I guess you have more luck looking for this information on the IBM site. Like this:

http://www.ibm.com/search?v=14&en=utf&lang=en&cc=us&hpp=10&catx=BAzw9zt3zE8z86zP9zCB&q=migrate+sql+server&cp=&lv=c&cat=w9&x=12&y=13