The row size limit comes into play if the DATA exceeds 8096 bytes not if the STRUCUTRE exceeds 8096 bytes.

I seem to recall that for TEXT and NTEXT only 16...

Thanks Noggin, that fixed it

Use the TEXT or NTEXT datatype. In SQL2005 use VARCHAR(MAX) or NVARCHAR(MAX).

This gives you 2GB of text.

In SQL2000 the text itself is not stored in the row, only the...

I thought that the @@RETURN_VALUE is intrinsic to the RETURN statement. I didn't think you could set it at will.

I tend to use positive values greater than zero to...

I was revisiting the problem I posed in http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=21&messageid=229499

The child table has an identity field called SelectionId which isn't mentioned in the schema at all and yet the bulk...

"Good" and "cursor" in the same sentence.

"Old Fashioned" is OK, it implies that something has worked

You can emphasise standards as much as you like with regard to XML but this is a data entry issue.

If you have required fields on a form within an application...

This might work a bit faster

DECLARE @ProcName sysname ,

@usercredentials sysname

set @procname=''

set @usercredentials='Development'

WHILE @procname is not null

begin

SELECT @procname = min(name)

FROM sysobjects

WHERE xtype='P' and name > @procname and name not like 'dt_%'

IF...

I take your point but DATTIME fields can hold values up to 31-Dec-9999. If you use a date that ridiculously far in the future then you DATEDIFF should always...

Have you considered using LIKE %[^0-9]% as a comparison?

In otherwords if your string contains characters in that are not digits?

I don't know how big your database is but in a live transaction database I would put the growth at fixed growth rather than a percentage.

I have come across this...

I don't have SQL Server available as I write this but my approach would be to do a DATEDIFF between a fixed date in the future and your time col...

I seem to remember that there was a thread about it once before but can't find it now.

The E is something to do with powers of 10. 1E1 =...

Basically NVARCHAR is a double-byte version of VARCHAR.

Some procedures demand that an NVARCHAR is passed and sp_executesql is one of them

If you run

sp_executesql 'SELECT * from sales'

you get an error...

SmallDateTime stores date/time value accurate to the minute

DateTime stores date time values accurate to 3 milliseconds.