![]() ![]() Be careful about encoding of the data file.You'll need to remove any CREATE FUNCTION statements and translate the algorithms manually. Database functions / Stored Procedures do not translate between RDBMS platforms.I don't know if SQL Server has CREATE SEQUENCE, so you may have to remove those. I'm not sure if they are equivalent, but if your original schema is full of 'id' fields, you may be in for some trouble. In SQL Server, this is an IDENTITY column, but they're not exactly the same thing. PostgreSQL does auto-increment fields by linking a NOT NULL INTEGER field to a SEQUENCE using a DEFAULT.Some things that I would expect to be an issue, however (obviously, NOT an exhaustive list): Unfortunately, I cannot help with which errors you may see as I have never gone from PostgreSQL to SQL Server, only the other way around. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |