Yeah, I saw that one and I was tempted to add an evil reply...

... but it's...

See http://msdn.microsoft.com/en-us/library/dd171921(SQL.100).aspx :

Using SET Options to Obtain Consistent Results

Evaluating the same expression can produce different results in SQL Server if different SET options are enabled for the current session when...

This should do the trick:

-- set up temporary table with database name

CREATE TABLE #databases (

database_name sysname

)

INSERT INTO #databases VALUES ('tempdb')

-- prepare the statement

DECLARE @sql nvarchar(max)

SELECT @sql = 'EXEC ' +...

It's not easy and has hidden pitfalls.

I strongly suggest to take a look at this great article by Paul White.

http://sqlblog.com/blogs/paul_white/archive/2010/10/19/sequence-tables.aspx

Hope this helps

Gianluca

You probably have a DDL trigger in place. Disable the trigger and you should be fine.

I would check:

1) Do the statements match EXACTLY?

2) Do you have the same exact SET options ON in SSMS and sqlcmd?

Can you post the actual execution plans? You should see...

SQLkiwi (9/7/2011)

Depends how you are specifying the hash join: OPTION (HASH JOIN)...

You could try to use a lower batch size. This will use less log space (in simple recovery).

The parameter name is BATCHSIZE. See BULK INSERT in BOL for more details.

Another...

Logical backups are a snapshot of data and metadata. To restore a logical backup you have to read the dump file and port it back into a working database by...

Stats may be outdated or insufficient.

You could:

A) UPDATE STATISTICS

B) Check if you need a multicolumn or filtered statistic, which are not created automatically by SQL Server.

Also, can you post...

You could use bulk insert or SSIS. If it's a one off operation, you could use the import/export wizard.

Have you tried any of these?

Congrats, Gail.

Your pace is unsustainable for us mere mortals.

Congrats, Roy!

Ninja's_RGR'us (9/6/2011)

How could it possibly work? the value is auto-generated & maintained by the server!

BEGIN TRAN

CREATE TABLE dbo.Boom...

What about adding the column with NULL? Would that work?