jtuttle99
asked on
conversion from int to uniqueidentifier is not supported
I got this error when I try to convert from Int to Uniqueindenfifier
I googled ant It seems that everyone wants to know why I want to convert.
I had Access Database and converted to SQL server data.
During the conversion, Autonumber Primary Key (unique, inedxed) in Access was converted Int in SQL.
Do I have to make new Column and set Primary key?
If so, is it possible to import the data from existing column?
I'm using SQL server 2008 express edition.
Thank you
I googled ant It seems that everyone wants to know why I want to convert.
I had Access Database and converted to SQL server data.
During the conversion, Autonumber Primary Key (unique, inedxed) in Access was converted Int in SQL.
Do I have to make new Column and set Primary key?
If so, is it possible to import the data from existing column?
I'm using SQL server 2008 express edition.
Thank you
Aneesh
why do u want to change the PK field from integer to uniqueidentifier, (unless you have merge replication / or a cube )
Hello jtuttle99,
int and uniqueidentifier are completely different data types, and cannot be converted from one to another.
As aneesh points out, the uniqueidentifier data type is mostly used for replication.
If your long integer AutoNumber in Access worked for you, then using int is entirely appropriate in SQL Server.
Regards,
Patrick
int and uniqueidentifier are completely different data types, and cannot be converted from one to another.
As aneesh points out, the uniqueidentifier data type is mostly used for replication.
If your long integer AutoNumber in Access worked for you, then using int is entirely appropriate in SQL Server.
Regards,
Patrick
ASKER
I'm new to SQL and I thought uniqueidentifier in SQL is for Autonumber(unique, indexed) in Access.
So, if I want to make the column (in this case BlogID) as Autonumber in Access, what kind of property do I need to add in Int? I want to make it automatically generate.
Thank you for your help!
jtuttle99,
Set up that column as identity. That will force the column to auto-increment as in Access.
Regards,
Patrick
Set up that column as identity. That will force the column to auto-increment as in Access.
Regards,
Patrick
ASKER
Before I save the column, could you tell me what will happen to the existing data?
Do I have to set Identity seed to the last existing # or does it automatically detect the last #?
Do I have to set Identity seed to the last existing # or does it automatically detect the last #?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I could create new table and set identity, but I would like to use the table (or data) I converted from Access.
Once I create a new table and set the int as identity, can I import other column's data( converted from Access) to the new table?
I tried...
1, I tried changing blogID's(converted from Access) "IS Identity" property to Yes, I get an error as follow.
"Saving changes is not permitted. The changes you have made required the following tables to be dropped and re-created. You have either made changes to a table that can't be re-created or enabled the option Prevent saving changes that require the table to be re-created."
2, I added new column to the table(converted from Access) and set the int as "Is Identity"
I get same error as above.
3, So, I created new table as Mark showed me but I can't import the rest of the data that I converted from Access.
Thank you so much for your help.
ASKER
Glad to hear it - was asleep "down under" while you were going through the above, apologies for the silence, and very happy to have been of help...