I am executing a DTS package every hour but I do not know
if there is a better way of doing, the ms sql are in the
factory floor they only hold for a week, so i need to send
all the data to the main sql, i think the dts sends the
whole database every time, Is that right? How can I send
the new data since last time was updated?
Thanks
Amadeo

You might consider looking into log shipping or replication, if you require
an hour latency log shipping or transactional replication might be the best
bet.

Some URL's

http://msdn.microsoft.com/library/de...lover_694n.asp

http://support.microsoft.com/default...b;en-us;314515

http://www.microsoft.com/downloads/d...b-2056adf73f94

http://www.sql-server-performance.co...g_shipping.asp

http://msdn.microsoft.com/library/de...server2000.asp



--
Ray Higdon MCSE, MCDBA, CCNA
---
"amadeo" <amadeocruz (AT) hotmail (DOT) com> wrote

DTS will take what you tell it to take. Sure you can take the whole DB or
just small portions of it.

Do you have Many "Floor" based SQL Servers and want to replicate the data to
a single main repository ?
For what do you want to use that repository?

If it's reporting then Log Shipping is a pain and Logs cannot be restored
whilst people are in the DB running reports which means you either kick them
out or wait for them to finish.

Is the data held in the "Floor" SQL Servers partitioned i.e. is everybody
working with the same data? If yes then when you pump back to the
Repository how do you handle conflicts? I update a customer/product and so
do you. Who does the repository see?

If the data held in the repository is simply going to be 1 SQL Server with
many databases i.e. copies of your "Floor" DBs then this is not a problem.

You have choices here based on what it is you require in no particular
order.

1. DTS
2. All 3 types of replication depending on the requirement you have
3. Log Shipping.

--

----------------------------
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org



"amadeo" <amadeocruz (AT) hotmail (DOT) com> wrote

I agree with Allan, log shipping is not the choice if you plan on using this
for reporting purposes, if this is for redundancy/failover purposes log
shipping works fine.


--
Ray Higdon MCSE, MCDBA, CCNA
--
"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote

How can I take small portions of the db?
The DB's in the floor are logging information of different
process A and B, these are regular workstations. The
server C is in the main office and it is a regular server
with raid and tape backup . I am taking the tables from
the database X in server A and the tables Y in server B,
and copying (merging) into a single database Z in server
C,so they see only one database. The network sometimes is
not reliable and that the reason we decide to log the info
in the production floor and ship it every hour, we were
sending the info directly to the server C but the network
bandwidth is not enough (still coax) so we decide for this
aproach, we need to be sure the data is log regardless of
the network.
Thanks

I would use snapshot replication based on your post, check out this
page. --http://www.mssqlcity.com/Articles/Replic/SetupSR/SetupSR.htm

HTH

Ray Higdon MCSE, MCDBA, CCNA

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

Ahhhhhhhh so you MERGE the data.

There is a big hint in the capitalisation. The only thing you need to
decide is

Conflict ? Who wins ?

If there are no conflicts and like you say the processes are split between
"floor" DBs then you can quite happily pump data to the repository happy in
the knowledge that they are the only ones to use that data.


--

----------------------------
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org



"Amadeo" <amadeocruz (AT) hotmail (DOT) com> wrote