http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=24

Well, I knew you hadn't. 

Here's the syntax from BOL:

ALTER TABLE table

{ [ ALTER COLUMN column_name

    { new_data_type [ ( precision [ ,...

DECLARE @seconds int

SET @seconds = 423456

SELECT CONVERT(char(8),DATEADD(s,@seconds,0),8)

Lars--

If you make changes to your design using ALTER TABLE, just save the scripts so you can apply them to all relevant databases.

Did you test this?

I found what really makes a difference with my local Developer Edition is the 7200rpm drive in my new T41p laptop (with 1.5GB RAM). 

Off-topic? ...

Did you bcp data into the table at some point?  I believe there was a bug where bulk loading allowed impossible values into datetime columns.  An impossible datetime value is...

http://www.sqlservercentral.com/columnists/awarren/worstpracticesobjectsnotownedbydbo.asp

Passwords will be case-sensitive if the server (or instance) is created with a case-sensitive collation.

use tempdb

go

CREATE TABLE Test(

Id int IDENTITY PRIMARY KEY,

Dt datetime)

INSERT Test(Dt) VALUES('20030808')

ALTER TABLE Test ALTER COLUMN Dt varchar(50)

UPDATE Test SET Dt = CONVERT(char(10),CAST(Dt AS datetime),101)

> select * from test where chkdate between '20040106' and dateadd(s, -1, '20040107')

This might work with smalldatetime values, but it will possibly exclude some datetime values for that date.  See my predicates...

The ANSI schema views work pretty well for this sort of thing...

SELECT Column_Name

FROM Information_Schema.Columns

WHERE Table_Name = 'SnapshotNbsMsMsALL'

ORDER BY Ordinal_Position

I guess not everyone's asleep.

There are two good reasons for not using LIKE with temporal values, even though it's recommended in BOL.

• In order...

> Is bit a valid ANSI-SQL type?

No. 

Try first replacing the doubled bars with something (like your tilde) not used in the data.  Then replace the single bars with two.  Finally replace the tilde with two bars.

declare @c...