Updates not working - invalid syntax

[1DMF]

I have just had to restore a table from a backup by importing the table as our server support people are incompetent and not backing it up properly nor know how to restore SQL.

So I hoped after importing the table, DbSchema would fix the problems, recreate keys , relationships etc, only it doesn't

It fails with errors and doesn't make required changes to the DB.

here is the error

java.sql.SQLException: Incorrect syntax near the keyword 'IDENTITY'.

Perhaps this is related to the 'Mandatory - not null' bug?

Thanks,
1DMF

[donose.mihai]

A beta update will be available tomorrow, if you can please post the full query that dbschema is trying to execute, hope it's the same issue for null / not null.

[1DMF]

There still seems to be updating problems. (having updated with the latest patch)

I am not able to modify the datatype of a PK.

I had to go to SQL Studio Manager and make the change as DbSchema kept moaning ....

ALTER TABLE ALTER COLUMN Packager failed because one or more objects access this column. The object 'PK_Packagers' is dependent on column 'Packager'.

Also it is still erroring when trying to make alterations to an Identity column with

Incorrect syntax near the keyword 'IDENTITY'.

[donose.mihai]

Can you please generate a table or two that you're having problem with and post what columns are you having problems with?

Thanks

[1DMF]

You can't even edit a PK that is auto increment and change it to no longer be an IDENTITY, the option is ghosted out?

This is on ANY table, do you not have SQL to try it yourself?

[donose.mihai]

We do have but it worked for us.

Update to the latest beta, some changes has been made for the autoincrement option (PK).

[1DMF]

Hi,

I have the latest version, the option to remove auto increment is ghosted when editing a PK Identity column?

Edit -> Just a thought, is it because I have to drop the PK_Index before I can alter the column.

I just found I couldn't alter a PK datatype from nvarchar to varchar or change its size constraint, with a message that other places were dependent on this column.

I deleted the PK Index and removed the PK against the colum, I was then able to make the required changes, then I set the PK back and it auto generated another PK_Index.

[donose.mihai]

I'll create a ticket for our developers maybe they can put an advice.

[albertstien3329]

SERIAL columns create as SERIAL but with default value, also created sequence for table