Developer forum

Forum » Development » Quick question: Negative effects on creating an index on DW7.2

Quick question: Negative effects on creating an index on DW7.2

E-mail notifications
Steen Nørgaard Perdersen
Reply
Posted on 13/06/2013 10:50:48

Hi All,

 

The specialist at Dynamicweb is out of the house to day, but reaearch has showed that creating this index on a DW version 19.2.8.2 resolves issues with indexing products:
 

USE [thedatabasename]

GO

CREATE NONCLUSTERED INDEX EcomOrderLines_OrderLineProductID

 

 

ON [dbo].[EcomOrderLines] ([OrderLineProductID])

INCLUDE ([OrderLineProductVariantID])  

GO

 

 

Can anyone think of negative side effects?

 

Best regards,

Steen/Bleau


Replies

 
Nicolai Høeg Pedersen
Posted on 13/06/2013 12:50:41
Reply
This post has been marked as an answer

None, except nonclustered indexes are not compatible with SQL-Server on Azure.

 

Any reason why it is nonclustered opposed to clustered?

 

BR Nicolai

Votes for this answer: 1
 
Steen Nørgaard Perdersen
Posted on 13/06/2013 12:55:08
Reply

 

Thanks...

 

The sql sentence was constructed by HostNordic who helped investigate(or a tool of theirs) .... I personally don't have the knowlegde to argue.... You would recommend clustered?

 

//Steen

 
Nicolai Høeg Pedersen
Posted on 13/06/2013 14:25:11
Reply

If clusterede do the trick, you should use that.

 

You must be logged in to post in the forum