>>>>Hi,
>>>>
>>>>I know I have done this type of change before (on some other customers' server) but this time I am hitting a wall. I need to set a column of a table to be Identity (that table is empty).
>>>>
>>>>But when I connect to the customer SQL Server, go to SSMS - connect using SQL server authentication. My SQL Server password has the following roles set in the database:
>>>>db_datareader, db_datawriter, db_owner.
>>>>Yes, when I try to set the PK column of a couple of table to Identity I am denied.
>>>>
>>>>What am I missing? TIA.
>>>
>>>Reading your question again..
>>>
>>>Odd. Is the column already set as a primary key? If so, remove the key and then set as identity, and then set as primary key.
>>>
>>>The column must be int or double by the way.
>>
>>My the way my Primary Identity column is numeric(6,0) and it works.
>
>I guess having 0 decimals is OK. News to me. I've always used int (or double if int wasn't big enough).
I would like to change this column to Integer but I have to keep it in sync with VFP database. And in the VFP database it is numeric(6,0).
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham