WhiteLotus (8/3/2014)
SQLRNNR (8/3/2014)
Did you check the status of the index creation while in progress? Did you check for blocking?Does the dev server have just a small amount of RAM or little cpu power?
Those things can affect the creation of the index.
Besides the 172million records, we know so little about your table. Things like total size of the table, data types, what the index was that you created. Those things can also impact the creation time.
Run the script from the following link and post the results for the table in question. Also post things like the table definition and index definition please.
the dev server has only 4 CPU with 8 GB of RAM
but the production has 24 CPU with 32 GB of RAM
How do i check the blocking when I run the index creation process?
Data for the table :
Index space : 32.067.563 MB
Row count : 178.432.356 MB
Data space : 10.905.453 MB
The index :
CREATE NONCLUSTERED INDEX [IX_D] ON [dbo].[D]
(
[TemplateId] ASC
)
INCLUDE ( [Value],
[Datestamp])
FYI :
Template id (int)
Value (varchar(2000)
datestamp (datetime )
Unfortunately when I run the script that u gave me ..I got many errors but i hope the table profile that I give you can give you more information
looking forward your response
thankss
It looks like you have a lot of off row data involved in that index creation. Looks to be a large index on a machine with little resources.
As per the other script, it looks like the update to the code engine converted > to gt and < to lt in the code. That would be the cause for the errors you are seeing. I am looking for a fix for that code prettifier to fix it.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events