Though it appears to be a warning while table creation, update & Inserts will fail with error

Cannot create a row of size xxxx which is greater than the allowable maximum...

This would be error message you will get if you start a transaction in any other level and then changes isolation level to snpshot; at statement level with table hint...

hey mike

What is problem with soln suggested by Darryl? 

declare

@option int

set

@option = 1

SELECT

*

Hi Michal

I don't think its possible to define snapshot isolation as table hint, it is feature enabled/disabled at database level. Can you please tell us why do u want this table...

SQL Server supports Float data type values ranging from -1.79E + 308 through 1.79E + 308 & Real allows Floating precision number data from 3.40E + 38 through 3.40E + 38....

Hi John

  Heard of Row versioning in SQL 2005? Snapshot isolation does provide it. The following document would give you an idea of how to handle snapshot isolation in sql 2005....

The document prefers to have temp table created first and then push data using Insert into Select query. I would prefer it to have Select into..from quety for creating...

Hi AndyDev

     Though your code is looking nice by splitting tasks in two sps, It could become a bottleneck if you use Insert..Exec to get results of both sps...

can you please paste execution plan of both queries?  

JMeyer32,

You must be getting errors with severity 20-25, as they terminates the database connection CATCH block could not handle them.    

Hi Jules

SQL BOL: Returns the number of characters, rather than the number of bytes, of the given string expression, excluding trailing blanks.

In your exmaple space appeared to be last character...

if you are using SQL 2005 better you use ALTER INDEX than DBCC DBREINDEX as it would be removed from future version, more over ALTER INDEX does provide online index...

SQL server marks each log record with Log Sequence Number.Every modification to database is logged, it can be anything like creating, committing, rollbacking transactions or backup, restore, or allocating pages...

I guess, it must be related to Lock Escalation Threshold. Lock escalation threshold is 5000 locks for single reference of table or index by single T-SQL statement or when the number...

use DBCC TraceFalgs 1211,1224 for disabling lock escalations to higher levels. For more information http://blogs.msdn.com/sqlserverstorageengine/archive/2006/05/17/Lock-escalation.aspx

Feature is not there in SQL 2000.