The code works for me. The table is created correctly.

That's incorrect. You should include the schema name when you...

You can safely remove those.

SELECT

'DROP INDEX ' + QUOTENAME(name) + ' ON ' + QUOTENAME(OBJECT_NAME(object_id))

FROM

sys.indexes

WHERE

is_hypothetical = 1;

You cannot export more than 256 columns to Excel.

http://msdn.microsoft.com/en-us/library/ms159836(v=sql.100).aspx

You can call msdb.dbo.sp_update_schedule

sp_update_schedule

It's possible they are hypothetical indexes, a remnant of database tuning advisor.

What does the following return?

SELECT

name,

is_hypothetical

FROM

sys.indexes

WHERE

OBJECT_NAME(object_id) = 'ABCTable'

Matt Crowley (10/31/2013)

---

Only one other thing to add to this, just be sure you are migrating to an Enterprise edition SQL Server, as I do not believe that compression is...

What about creating a stored procedure database on your server.

1. Loop through sys.procedures for _del_

2. Fetch text from syscomments definition from sql_modules

3. Create proc on stored procedure database

4. Delete procedure...

Jeff Moden (10/31/2013)

---

+1. I don't know what others call the type of function you wrote for the "Apply" function but I call them "iSF" or "Inline Scalar Function". ...

It is much faster to apply a table function.

CREATE TABLE Test1 (ID INT);

GO

INSERT INTO Test1

SELECT TOP 1000000 ROW_NUMBER() OVER (ORDER BY a.object_id)

FROM sys.all_columns a

CROSS JOIN sys.all_columns b

GO

CREATE FUNCTION UDF_INLINE (@Input...

Jerry

Jeff Moden (10/30/2013)

---

martin catherall (10/30/2013)

---

fair point Jeff, I used the term "spill to disk" to mean "spill to tempdb" - that was an error on my part.

Let me re-phrase again...

Your tempdb usage has nothing to do with cardinality estimates. It is because you are ordering by a NVARCHAR(2000) column and the sort operation is spilling to tempdb. Try the...

Richard Warr (10/29/2013)

---

You make a valid point but it reminds me...

:Whistling: