Vic, this is awesome insight. Thanks so much! -bws
--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix
bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Vic Drecchio
Sent: Thursday, November 20, 2008 4:31 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Deleting Data in MSSQL
When inserting data (properly) via SQL (I do it all the time), you'll
see triggers on most of the tables that require the
PROGRESS_RECID_IDENT_ AND PROGRESS_RECID columns. These triggers
populate those fields automatically and in the case of other Sequential
population (Like LaborHed/LaborDtl), it will hit the corresponding table
in the database that is prefixed with _SEQT_xxxxxxxx
These tables can be seen with SQL Mgmt Studio. These tables keep track
of the latest ID's used to avoid duplication.
Since they are triggers for INSERTS, they will fire anytime a new record
is inserted automatically and unbeknownst to you. They will
auto-populate those Progress fields.
You'll see triggers on almost every table that handle this. I have also
altered some of my triggers to further auto-populate some UD fields by
going out and selecting values from other tables. I love Vantage SQL
for these reasons.
Always backup prior. Always test in TEST multiple times for every
possible scenario. Play in TEST to see any anomalies. All good? Port
it over to LIVE. Also, I always populate a UD field when I do this so I
can quickly identify "my inserts" and delete if necessary.
Work step-by-step in the Query window and just be careful and you will
be OK.
For us SQL folks, Progress is simply a schema holder, nothing more.
It's a middle man.
[Non-text portions of this message have been removed]
--
Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix
bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Vic Drecchio
Sent: Thursday, November 20, 2008 4:31 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Deleting Data in MSSQL
When inserting data (properly) via SQL (I do it all the time), you'll
see triggers on most of the tables that require the
PROGRESS_RECID_IDENT_ AND PROGRESS_RECID columns. These triggers
populate those fields automatically and in the case of other Sequential
population (Like LaborHed/LaborDtl), it will hit the corresponding table
in the database that is prefixed with _SEQT_xxxxxxxx
These tables can be seen with SQL Mgmt Studio. These tables keep track
of the latest ID's used to avoid duplication.
Since they are triggers for INSERTS, they will fire anytime a new record
is inserted automatically and unbeknownst to you. They will
auto-populate those Progress fields.
You'll see triggers on almost every table that handle this. I have also
altered some of my triggers to further auto-populate some UD fields by
going out and selecting values from other tables. I love Vantage SQL
for these reasons.
Always backup prior. Always test in TEST multiple times for every
possible scenario. Play in TEST to see any anomalies. All good? Port
it over to LIVE. Also, I always populate a UD field when I do this so I
can quickly identify "my inserts" and delete if necessary.
Work step-by-step in the Query window and just be careful and you will
be OK.
For us SQL folks, Progress is simply a schema holder, nothing more.
It's a middle man.
[Non-text portions of this message have been removed]