I have a project that requires to send dataset that meet certain criteria
stored in SQL Server 7.0 in my office at L.A. to the parent company's SQL
Server 2000 at TX and then update parent's dataset that has been sent before
monthly for whatever changes that have been made over the time. Can somebody
teach me a way how to do it? As I don't know which record what data value has
been changed at our office over the time so as to update the dataset at TX's
SQL Server. It definitely will have changes. Also our SQL Server has limited
resource and the transmitted dataset will be about 400-500K records at the
first population.
Thank you in advance for your help.
Take a look at DTS if you want to try to automate the process.
If you would like to do it by hand, I would suggest that you use bcp to move
the data out to a flat file, WinZip the file and ship it. On the TX
system, bcp that new data into a staging table and then perform your
updates.
Note: Before performing your updates, you should probably back up the TX
database. That way if you really do something strange, you can quickly undo
it.
Rick Sawtell
MCT, MCSD, MCDBA
"Emily" <Emily@.discussions.microsoft.com> wrote in message
news:6CDB8949-4450-4F4E-9A07-F67950847298@.microsoft.com...
> I have a project that requires to send dataset that meet certain criteria
> stored in SQL Server 7.0 in my office at L.A. to the parent company's SQL
> Server 2000 at TX and then update parent's dataset that has been sent
before
> monthly for whatever changes that have been made over the time. Can
somebody
> teach me a way how to do it? As I don't know which record what data value
has
> been changed at our office over the time so as to update the dataset at
TX's
> SQL Server. It definitely will have changes. Also our SQL Server has
limited
> resource and the transmitted dataset will be about 400-500K records at the
> first population.
> Thank you in advance for your help.
|||Thanks for your help. But how can I tell which record has changes and
requires to do an update to the TX's database?
B.Regards,
Emily
"Rick Sawtell" wrote:
> Take a look at DTS if you want to try to automate the process.
> If you would like to do it by hand, I would suggest that you use bcp to move
> the data out to a flat file, WinZip the file and ship it. On the TX
> system, bcp that new data into a staging table and then perform your
> updates.
> Note: Before performing your updates, you should probably back up the TX
> database. That way if you really do something strange, you can quickly undo
> it.
> Rick Sawtell
> MCT, MCSD, MCDBA
>
> "Emily" <Emily@.discussions.microsoft.com> wrote in message
> news:6CDB8949-4450-4F4E-9A07-F67950847298@.microsoft.com...
> before
> somebody
> has
> TX's
> limited
>
>
|||Without looking at your table structures and how the data is handled, I
couldn't tell you.
How would you do it normally?
You could use a RowVersion datatype in the tables at both sites and then
compare them. For RowVersions that are different, you could perform your
updates on those rows.
HTH
Rick Sawtell
"Emily" <Emily@.discussions.microsoft.com> wrote in message
news:B40AE998-4ABF-4DC8-8954-4F0E938018C3@.microsoft.com...[vbcol=seagreen]
> Thanks for your help. But how can I tell which record has changes and
> requires to do an update to the TX's database?
> B.Regards,
> Emily
> "Rick Sawtell" wrote:
move[vbcol=seagreen]
TX[vbcol=seagreen]
undo[vbcol=seagreen]
criteria[vbcol=seagreen]
SQL[vbcol=seagreen]
value[vbcol=seagreen]
at[vbcol=seagreen]
the[vbcol=seagreen]
|||The recordset is pulled from different tables by joining the foreign keys
with the main table. None of them has a column with timestamp datatype( I
guess this is the datatype that you refer to as there is no RowVersion
datatype in SQL Server 7.0) .
Correct me if I'm wrong.
All tables that are used to get the recordset have a primary key in integer
datatype like an autonumber but not include in the recordset.
Does it mean we should add an additional column to trigger if there is any
change?
Thank you very much for your help.
Emily
"Rick Sawtell" wrote:
> Without looking at your table structures and how the data is handled, I
> couldn't tell you.
> How would you do it normally?
> You could use a RowVersion datatype in the tables at both sites and then
> compare them. For RowVersions that are different, you could perform your
> updates on those rows.
> HTH
> Rick Sawtell
>
> "Emily" <Emily@.discussions.microsoft.com> wrote in message
> news:B40AE998-4ABF-4DC8-8954-4F0E938018C3@.microsoft.com...
> move
> TX
> undo
> criteria
> SQL
> value
> at
> the
>
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment