Custom column fields
olavz
Posts: 2
Hello all,
I've got a question regarding syncing column fields in a table.
I love using the SQL compare tool (I use version 10.x) but there's one limitation, as far as I know and understand, that I cannot resolve.
Maybe somebody knows a solution for it. So here we go.
My databases contain mostly the same fields in all tables, but sometimes I have to create some custom tables but also some custom fields in the 'standard' tables for some customers who wish to have custom software and fields.
When we are releasing the next version of the software I generally use SQL compare to sync all databases. This works just fine for most cases since I can filter out the custom tables.
But the tables with "custom" fields are a problem. Please see the example below. The fields with "custom" in it should not dissapear when syncing tables.
Target DB:
CREATE TABLE [dbo].[tbl_Order](
[ord_Id] [int] IDENTITY(1,1) NOT NULL,
[ord_kla_Id] [int] NOT NULL,
[ord_tar_Id] [int] NULL,
[ord_Custom_TypeOrder] [int] NULL,
[ord_Custom_NotificatieType] [int] NULL
etc..
"General" DB for next release:
CREATE TABLE [dbo].[tbl_Order](
[ord_Id] [int] IDENTITY(1,1) NOT NULL,
[ord_kla_Id] [int] NOT NULL,
[ord_tar_Id] [int] NULL,
[ord_NEWFIELDHERE] [int] NULL
etc..
So, when I use SQL compare I will lose my "custom" fields, which is a problem. Can somebody tell me if there's an easy solution for this?
Kind regards,
Olav Zuijdam
I've got a question regarding syncing column fields in a table.
I love using the SQL compare tool (I use version 10.x) but there's one limitation, as far as I know and understand, that I cannot resolve.
Maybe somebody knows a solution for it. So here we go.
My databases contain mostly the same fields in all tables, but sometimes I have to create some custom tables but also some custom fields in the 'standard' tables for some customers who wish to have custom software and fields.
When we are releasing the next version of the software I generally use SQL compare to sync all databases. This works just fine for most cases since I can filter out the custom tables.
But the tables with "custom" fields are a problem. Please see the example below. The fields with "custom" in it should not dissapear when syncing tables.
Target DB:
CREATE TABLE [dbo].[tbl_Order](
[ord_Id] [int] IDENTITY(1,1) NOT NULL,
[ord_kla_Id] [int] NOT NULL,
[ord_tar_Id] [int] NULL,
[ord_Custom_TypeOrder] [int] NULL,
[ord_Custom_NotificatieType] [int] NULL
etc..
"General" DB for next release:
CREATE TABLE [dbo].[tbl_Order](
[ord_Id] [int] IDENTITY(1,1) NOT NULL,
[ord_kla_Id] [int] NOT NULL,
[ord_tar_Id] [int] NULL,
[ord_NEWFIELDHERE] [int] NULL
etc..
So, when I use SQL compare I will lose my "custom" fields, which is a problem. Can somebody tell me if there's an easy solution for this?
Kind regards,
Olav Zuijdam
