non-clustered-index

This is the query for creating index create index idx_ncl_2 on BFPRODATTRASSOCIATION (value,attributeid) include (productid) Table structure of BFPRODATTRASSOCIATION ProdAttrAssociationId bigint no 8 ProductId bigint no 8 AttributeId bigint no 8 Value varchar no 4096 I am getting this error: The maximum key length is 900 bytes. The index ‘idx_ncl_2’ has maximum length of 1237 bytes. I have to create a nonclustered index on this column. Is there any way i can create index for the column which have datatype of varchar and size is greater than 900. Please suggest. You can't - as the error message

It is possible to define non-unique columns as clustered as well as non-clustered indexes. However, SQL Server adds a 4 byte integer to the indexed columns in case of a clustered index, if the column is not defined as unique. This is done to keep the "uniqueness" of the record internally even though two or more records may have the value for that column. Why isn't this integer necessary in case of a non-clustered index? A non-clustered index already includes the clustered index column so it can reference the exact row that it correlates to. Hence with the uniquifier on the clustered index, the

I created a unique index (case description should be unique if IsDelete != 1) CREATE UNIQUE NONCLUSTERED INDEX [UniqueCaseDescription] ON [tblCases] ([fldCaseDescription] ASC) WHERE [IsDeleted] = CAST(0 AS varbinary(1)) WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, SORT_IN_TEMPDB = OFF, IGNORE_DUP_KEY = OFF, DROP_EXISTING = OFF, ONLINE = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] Then when I run the following procedure it throws 'UPDATE failed because the following SET options have incorrect settings: 'ARITHABORT'. Verify that SET options are correct for use with

I have a table 'users' with 'login' column defined as: [login] VARCHAR(50) UNIQUE NOT NULL Now I want to remove this unique constraint/index using SQL script. I found its name UQ_ users _7D78A4E7 in my local database but I suppose it has a different name on another database. What is the best way to drop this unique constraint? Or at least any... Thanks. SKINDER, your code does not use column name. Correct script is: declare @table_name nvarchar(256) declare @col_name nvarchar(256) declare @Command nvarchar(1000) set @table_name = N'users' set @col_name = N'login' select @Command = 'ALTER TABLE

I have a table in SQL Server database which I want to be able to search and retrieve data from as fast as possible. I don't care about how long time it takes to insert into the table, I am only interested in the speed at which I can get data. The problem is the table is accessed with 20 or more different types of queries. This makes it a tedious task to add an index specially designed for each query. I'm considering instead simply adding an index that includes ALL columns of the table. It's not something you would normally do in "good" database design, so I'm assuming there is some good reason

I know primary differences between clustered and non clustered indexes and have an understanding of how they actually work. I understand how clustered and non-clustered indexes improve read performance. But one thing I am not sure is that what would be the reasons where I would choose one over the other. For example: If a table does not have a clustered index, should one create a non-clustered index and whats the benefit of doing marc_s I just want to put in a word of warning: please very carefully pick your clustered index! Every "regular" data table ought to have a clustered index, since

This question already has an answer here: What are the differences between a clustered and a non-clustered index? 12 answers I need to add proper index to my tables and need some help. I'm confused and need to clarify a few points: Should I use index for non-int columns? Why/why not I've read a lot about clustered and non-clustered index yet I still can't decide when to use one over the other. A good example would help me and a lot of other developers. I know that I shouldn't use indexes for columns or tables that are often updated. What else should I be careful about and how can I know that