Replication Errors

Hello,
I am getting the following error when trying to sync from my local site to
my dr site.
Could not locate entry in sysdatabases for database '10.1.200.70'. No entry
found with that name. Make sure that the name is entered correctly.
(Source: 10.1.200.70 (Data source); Error number: 911)
I am trying to setup replication from my local site to my DR site. I can
register my dr sql box using the IP but not the hostname.
Any thoughts on this error?
Lontae,
try creating an alias for the server's IP address. You might also need an
entry in the hosts/lmhosts (I can't remember which to locate the snapshot
share.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Alias in DNS?
"Paul Ibison" wrote:

> Lontae,
> try creating an alias for the server's IP address. You might also need an
> entry in the hosts/lmhosts (I can't remember which to locate the snapshot
> share.
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
>
|||Lontae,
alias in the server network utility (I'm sure you now this but if not it's
located at start, programs, microsoft sql server...).
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I think Paul means client network utility
Easy mistake to make, I've made it thousands of times, myself.
For netbios resolution use lmhosts (ie a unc snapshot), for ftp use hosts.
name resolution goes through a sequence so it really doesn't matter as both
files are checked, but there are slight performance increases (milli
seconds) if you make the correct entries.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:umx%23oCGvEHA.940@.TK2MSFTNGP14.phx.gbl...
> Lontae,
> alias in the server network utility (I'm sure you now this but if not it's
> located at start, programs, microsoft sql server...).
> HTH,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Thanks Hilary,
I'm not sure about the setup, but Lontae is registering
the DR site at the local site so I was thinking it was
push rather than pull.
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Replication Errors

I have three questions?
1. I have a Sql server instance running without any name, it just has a
default name (local), when i try to go configure replication its says that
replication does not support (local) name. This server is in production
right now. And it will be hard to shut it down. Is there anyway to change
the name of the instance? Even if i unregister and re-register a new
server, will all my databses and plans, etc. will be the exact same as on
the last instance? Whats the best possible way can i configure replication
on this instance?
2. I was subscribed to a couple push subscriptions replication from a
different server, but that server no longer exists, but my server still goes
out and looks for the subscription, I tried to remove the subscription, but
i get the same errror like on the question one, "replication does not
support (local) name." so i can't remove the subscription. What can i do to
remove this subscriptions?
3. When i try to configure the Replication, its says that Server Agent uses
the local service account you need to change the account? Whats the Local
service account? Can two services not use the same local service account?
How do i need to set this up, to use the account? Do i need to create
another account?
Thanks for all your help.
See inline
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shash Goyal" <Shash703@.gmail.com> wrote in message
news:eiVPxa7vEHA.824@.TK2MSFTNGP11.phx.gbl...
> I have three questions?
> 1. I have a Sql server instance running without any name, it just has a
> default name (local), when i try to go configure replication its says that
> replication does not support (local) name. This server is in production
> right now. And it will be hard to shut it down. Is there anyway to change
> the name of the instance? Even if i unregister and re-register a new
> server, will all my databses and plans, etc. will be the exact same as on
> the last instance? Whats the best possible way can i configure
replication
> on this instance?
>
Every server has a name, the default name is the same as the name of the NT
server on which SQL runs... YOu simply have SQL registered in you SEM unding
(local) instead of the server name... Get the real servername, Un-register
it in SEM , then register it with the real name...
> 2. I was subscribed to a couple push subscriptions replication from a
> different server, but that server no longer exists, but my server still
goes
> out and looks for the subscription, I tried to remove the subscription,
but
> i get the same errror like on the question one, "replication does not
> support (local) name." so i can't remove the subscription. What can i do
to
> remove this subscriptions?
Re-register the server, and take a look at the sp_dropsubscription
> 3. When i try to configure the Replication, its says that Server Agent
uses
> the local service account you need to change the account? Whats the Local
> service account? Can two services not use the same local service account?
> How do i need to set this up, to use the account? Do i need to create
> another account?
> Set up a domain account for SQL Server. Add the domain account to each of
your SQL Servers as a SQL administrator. In SEM, go to SQL Agent and right
click and go to properties. I think the second tab is where you put the
login password ( instead of system checkbox.) Stop and re-start SQL Agent
and you should be good.
> Thanks for all your help.
>

Replication Errors

I have three questions'
1. I have a Sql server instance running without any name, it just has a
default name (local), when i try to go configure replication its says that
replication does not support (local) name. This server is in production
right now. And it will be hard to shut it down. Is there anyway to change
the name of the instance? Even if i unregister and re-register a new
server, will all my databses and plans, etc. will be the exact same as on
the last instance? Whats the best possible way can i configure replication
on this instance?
2. I was subscribed to a couple push subscriptions replication from a
different server, but that server no longer exists, but my server still goes
out and looks for the subscription, I tried to remove the subscription, but
i get the same errror like on the question one, "replication does not
support (local) name." so i can't remove the subscription. What can i do to
remove this subscriptions'
3. When i try to configure the Replication, its says that Server Agent uses
the local service account you need to change the account' Whats the Local
service account? Can two services not use the same local service account?
How do i need to set this up, to use the account? Do i need to create
another account?
Thanks for all your help.See inline
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shash Goyal" <Shash703@.gmail.com> wrote in message
news:eiVPxa7vEHA.824@.TK2MSFTNGP11.phx.gbl...
> I have three questions'
> 1. I have a Sql server instance running without any name, it just has a
> default name (local), when i try to go configure replication its says that
> replication does not support (local) name. This server is in production
> right now. And it will be hard to shut it down. Is there anyway to change
> the name of the instance? Even if i unregister and re-register a new
> server, will all my databses and plans, etc. will be the exact same as on
> the last instance? Whats the best possible way can i configure
replication
> on this instance?
>
Every server has a name, the default name is the same as the name of the NT
server on which SQL runs... YOu simply have SQL registered in you SEM unding
(local) instead of the server name... Get the real servername, Un-register
it in SEM , then register it with the real name...
> 2. I was subscribed to a couple push subscriptions replication from a
> different server, but that server no longer exists, but my server still
goes
> out and looks for the subscription, I tried to remove the subscription,
but
> i get the same errror like on the question one, "replication does not
> support (local) name." so i can't remove the subscription. What can i do
to
> remove this subscriptions'
Re-register the server, and take a look at the sp_dropsubscription
> 3. When i try to configure the Replication, its says that Server Agent
uses
> the local service account you need to change the account' Whats the Local
> service account? Can two services not use the same local service account?
> How do i need to set this up, to use the account? Do i need to create
> another account?
> Set up a domain account for SQL Server. Add the domain account to each of
your SQL Servers as a SQL administrator. In SEM, go to SQL Agent and right
click and go to properties. I think the second tab is where you put the
login password ( instead of system checkbox.) Stop and re-start SQL Agent
and you should be good.
> Thanks for all your help.
>sql

Replication Errors

I have three questions?
1. I have a Sql server instance running without any name, it just has a
default name (local), when i try to go configure replication its says that
replication does not support (local) name. This server is in production
right now. And it will be hard to shut it down. Is there anyway to change
the name of the instance? Even if i unregister and re-register a new
server, will all my databses and plans, etc. will be the exact same as on
the last instance? Whats the best possible way can i configure replication
on this instance?
2. I was subscribed to a couple push subscriptions replication from a
different server, but that server no longer exists, but my server still goes
out and looks for the subscription, I tried to remove the subscription, but
i get the same errror like on the question one, "replication does not
support (local) name." so i can't remove the subscription. What can i do to
remove this subscriptions?
3. When i try to configure the Replication, its says that Server Agent uses
the local service account you need to change the account? Whats the Local
service account? Can two services not use the same local service account?
How do i need to set this up, to use the account? Do i need to create
another account?
Thanks for all your help.
Hi Shash Goyal,
Most of your problems relate to having registered your server as "(local)"
in Enterprise Manager. Try reregistering it as the name of your computer
instead. I think that will fix problems 1 and 2. With the 3rd one, all it's
trying to tell you is that if you want to connect to anything outside your
computer, you normally need a domain user account. The "Local Service"
account is a special account on your computer that only applies to that
computer. Try creating a new user that will be used only as a service
account (ie something like "sqlservice" for a name). Make it a domain user
if you are in a domain. Give it appropriate permissions and change SQL
Server and SQL Agent to run as that user (you can do this by right-clicking
each in Enterprise Manager) and choosing the "Security" option.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Shash Goyal" <Shash703@.gmail.com> wrote in message
news:%23j6aiu5vEHA.3080@.TK2MSFTNGP12.phx.gbl...
>I have three questions?
> 1. I have a Sql server instance running without any name, it just has a
> default name (local), when i try to go configure replication its says that
> replication does not support (local) name. This server is in production
> right now. And it will be hard to shut it down. Is there anyway to change
> the name of the instance? Even if i unregister and re-register a new
> server, will all my databses and plans, etc. will be the exact same as on
> the last instance? Whats the best possible way can i configure
> replication
> on this instance?
>
> 2. I was subscribed to a couple push subscriptions replication from a
> different server, but that server no longer exists, but my server still
> goes
> out and looks for the subscription, I tried to remove the subscription,
> but
> i get the same errror like on the question one, "replication does not
> support (local) name." so i can't remove the subscription. What can i do
> to
> remove this subscriptions?
> 3. When i try to configure the Replication, its says that Server Agent
> uses
> the local service account you need to change the account? Whats the Local
> service account? Can two services not use the same local service account?
> How do i need to set this up, to use the account? Do i need to create
> another account?
>
> Thanks for all your help.
>

Replication Errors

I have three questions'
1. I have a Sql server instance running without any name, it just has a
default name (local), when i try to go configure replication its says that
replication does not support (local) name. This server is in production
right now. And it will be hard to shut it down. Is there anyway to change
the name of the instance? Even if i unregister and re-register a new
server, will all my databses and plans, etc. will be the exact same as on
the last instance? Whats the best possible way can i configure replication
on this instance?
2. I was subscribed to a couple push subscriptions replication from a
different server, but that server no longer exists, but my server still goes
out and looks for the subscription, I tried to remove the subscription, but
i get the same errror like on the question one, "replication does not
support (local) name." so i can't remove the subscription. What can i do to
remove this subscriptions'
3. When i try to configure the Replication, its says that Server Agent uses
the local service account you need to change the account' Whats the Local
service account? Can two services not use the same local service account?
How do i need to set this up, to use the account? Do i need to create
another account?
Thanks for all your help.See inline
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Shash Goyal" <Shash703@.gmail.com> wrote in message
news:eiVPxa7vEHA.824@.TK2MSFTNGP11.phx.gbl...
> I have three questions'
> 1. I have a Sql server instance running without any name, it just has a
> default name (local), when i try to go configure replication its says that
> replication does not support (local) name. This server is in production
> right now. And it will be hard to shut it down. Is there anyway to change
> the name of the instance? Even if i unregister and re-register a new
> server, will all my databses and plans, etc. will be the exact same as on
> the last instance? Whats the best possible way can i configure
replication
> on this instance?
>
Every server has a name, the default name is the same as the name of the NT
server on which SQL runs... YOu simply have SQL registered in you SEM unding
(local) instead of the server name... Get the real servername, Un-register
it in SEM , then register it with the real name...
> 2. I was subscribed to a couple push subscriptions replication from a
> different server, but that server no longer exists, but my server still
goes
> out and looks for the subscription, I tried to remove the subscription,
but
> i get the same errror like on the question one, "replication does not
> support (local) name." so i can't remove the subscription. What can i do
to
> remove this subscriptions'
Re-register the server, and take a look at the sp_dropsubscription
> 3. When i try to configure the Replication, its says that Server Agent
uses
> the local service account you need to change the account' Whats the Local
> service account? Can two services not use the same local service account?
> How do i need to set this up, to use the account? Do i need to create
> another account?
> Set up a domain account for SQL Server. Add the domain account to each of
your SQL Servers as a SQL administrator. In SEM, go to SQL Agent and right
click and go to properties. I think the second tab is where you put the
login password ( instead of system checkbox.) Stop and re-start SQL Agent
and you should be good.
> Thanks for all your help.
>

Replication Error

I have three questions?
1. I have a Sql server instance running without any name, it just has a
default name (local), when i try to go configure replication its says that
replication does not support (local) name. This server is in production
right now. And it will be hard to shut it down. Is there anyway to change
the name of the instance? Even if i unregister and re-register a new
server, will all my databses and plans, etc. will be the exact same as on
the last instance? Whats the best possible way can i configure replication
on this instance?
2. I was subscribed to a couple push subscriptions replication from a
different server, but that server no longer exists, but my server still goes
out and looks for the subscription, I tried to remove the subscription, but
i get the same errror like on the question one, "replication does not
support (local) name." so i can't remove the subscription. What can i do to
remove this subscriptions?
3. When i try to configure the Replication, its says that Server Agent uses
the local service account you need to change the account? Whats the Local
service account? Can two services not use the same local service account?
How do i need to set this up, to use the account? Do i need to create
another account?
Thanks for all your help.
1. Use the netbios name of the computer (select @.@.servername)
2. REgister the netbiosname as above in EM (after removing the local one).
3. This should be set as a domain user in settings, comtrol panel, admin
tools, services, SQLSERVERAGENT. This account should be a sysadmin in sql
server, and a local administrator. The easiest thing to do is to set the sql
server service and sqlserver agent to use the same account having the
attributes above.
You can use local system accounts to test replication when setting it up on
one machine.
Replication functions as a series of jobs running as the sql server agent,
so this account should have access to the snapshot share on the publisher
and access to the publication (more details in BOL, 'publication access
list' and 'replication security').
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
sql

REPLICATION ERROR

Hi,
I am dealing with merge replication between local & remote servers.
Last week the following error occurs two times.
The merge process could not perform retention-based meta data cleanup in
database 'TEST'.
(Source: Merge Replication Provider (Agent); Error number: -2147199467)
The merge process timed out while executing a query. Reconfigure the
QueryTimeout parameter and retry the operation.
(Source: TSERVER (Data source); Error number: 0)
First I gave 'start synchronizing' after that I restarted the merge agent
but no use .
Finally after restarting the server(publisher), it came to end. Now its
working fine.
My question is,
1. what is the reason for this error?
2. Is this a Symptom for future problems (ie., like database corruption)
but when I run CHECKDB command, no error has been shown. It says the DB
is fine.
Can any one advice me?
Thanks,
Soura.
This error is basically a timeout and can happen for many reasons. They
are usually assoicated with slow servers or subscribers but could also
be network problems. Reindexing your tables, especially
msmerge_contents, msmerge_Genhistory, msmerge_tombstone can help if you
have a lot of replication metadata. If you have a large amount of
metadata in those tables you can also run sp_mergecleanupmetadata. This
will cause you to generate and apply a new snapshot however. If you
choose to use the sp_mergecleanupmeta data and have a large number or
rows in your merge tables. You might want to truncate the
msmerge_contents and maybe the msmerge_genhistory table at the
publisher and subcribers before running as it will also get a timeout
doing the cleanup.
|||Hi Sounder,
I found this from One article.
In case of this error
stop the merge agent and do a dbcc dbreindex -- to all tables by using that
reindex procedure.
Thanks.
Herbert
"SouRa" wrote:

> Hi,
> I am dealing with merge replication between local & remote servers.
> Last week the following error occurs two times.
> The merge process could not perform retention-based meta data cleanup in
> database 'TEST'.
> (Source: Merge Replication Provider (Agent); Error number: -2147199467)
> ----
> --
> The merge process timed out while executing a query. Reconfigure the
> QueryTimeout parameter and retry the operation.
> (Source: TSERVER (Data source); Error number: 0)
> First I gave 'start synchronizing' after that I restarted the merge agent
> but no use .
> Finally after restarting the server(publisher), it came to end. Now its
> working fine.
> My question is,
> 1. what is the reason for this error?
> 2. Is this a Symptom for future problems (ie., like database corruption)
> but when I run CHECKDB command, no error has been shown. It says the DB
> is fine.
> Can any one advice me?
> Thanks,
> Soura.
|||Hi Sounder,
I find this from one article.
In case of these kind of error
stop the merge agent and do a dbcc dbreindex -- Do reindex to all tables
using that procedure
Thanks
Herbert
"SouRa" wrote:

> Hi,
> I am dealing with merge replication between local & remote servers.
> Last week the following error occurs two times.
> The merge process could not perform retention-based meta data cleanup in
> database 'TEST'.
> (Source: Merge Replication Provider (Agent); Error number: -2147199467)
> ----
> --
> The merge process timed out while executing a query. Reconfigure the
> QueryTimeout parameter and retry the operation.
> (Source: TSERVER (Data source); Error number: 0)
> First I gave 'start synchronizing' after that I restarted the merge agent
> but no use .
> Finally after restarting the server(publisher), it came to end. Now its
> working fine.
> My question is,
> 1. what is the reason for this error?
> 2. Is this a Symptom for future problems (ie., like database corruption)
> but when I run CHECKDB command, no error has been shown. It says the DB
> is fine.
> Can any one advice me?
> Thanks,
> Soura.

Replication ( Local to Hosting Company )

Hi,
I wanna replicate two SQL Server 2000 DB, On is in my Company behind a DSL
Router, the other is in a Machine on somewhere which I purchase as a Hosting
package..
Configuration of Local SQL Server is already Done by Me and Publication is
Created, I chose Snapshot one...
The problem is, How My remote SQL Server subscribe to the publisher, How can
I Subscribe and, If I can, How my Remote Server See my local Snapshot files
in order to get them in Remote DB, Should I send Snapshot files to Remote or
We have another solution ?
( Note that on Remote, I only can make a subscription, others are disabled )
What kind of solution do you propose ?
Have a look at this article: http://support.microsoft.com/?id=321822
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Configure your publication for an anoymous pull. Configure your ftp site for
anonymous access, and configure your publication to create the snapshot
within the ftp site.
Configure the subscriber for replication and then pull the subscription from
the subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"BonGee" <Bongee@.bonbon.n.e.t> wrote in message
news:ufJsvNI3EHA.3336@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I wanna replicate two SQL Server 2000 DB, On is in my Company behind a DSL
> Router, the other is in a Machine on somewhere which I purchase as a
> Hosting
> package..
> Configuration of Local SQL Server is already Done by Me and Publication is
> Created, I chose Snapshot one...
> The problem is, How My remote SQL Server subscribe to the publisher, How
> can
> I Subscribe and, If I can, How my Remote Server See my local Snapshot
> files
> in order to get them in Remote DB, Should I send Snapshot files to Remote
> or
> We have another solution ?
> ( Note that on Remote, I only can make a subscription, others are
> disabled )
> What kind of solution do you propose ?
>

Replication - SQLServer Agent uses System Account

When I attempt to set up replication on my local box, I receive the error -'SQLServer Agent uses the Systems Account, which causes replication betweem servers to fail'.
Why does this happen? And can I overcome this?
Thanks :)
BiancaStart SQLServerAgent service using a domain account. This account must have the appropriate rights on teh Publisher, Distributor and Subscriber computers (depending on the replication type)

Originally posted by Bianca_J
When I attempt to set up replication on my local box, I receive the error -'SQLServer Agent uses the Systems Account, which causes replication betweem servers to fail'.

Why does this happen? And can I overcome this?

Thanks :)

Bianca|||Thank you for your post :)

What is a Domain Account?

Is this set up in Windows 2000? And if I set up a Domain Account in my local Windows 2000 box - how do I have right over a remore server?

Thanks

Bianca

Replication - sp_MSget_subscription_guid impossible

We currently have a pull transactional subscription running from a remote 'PublicationServer' in another country to our local server.

After restarting our fire wall we get the following error message:
"The process could not execute '{call sp_MSget_subscription_guid(16)}' on 'PublicationServer'."

This message is followed by another error message: "Another distribution agent for the subscription(s) is running.", although nothing was changed to the configuration and no SQL processes were started or restarted.

When we restart the distribution job manually it runs as if nothing happened.

Does anyone know what exactly caused the failure, and how to prevent it ?

PhilipQuit restarting your firewall ?

I really don't have a good answer for this question. Sometimes after an unexpected failure, the simplest answer is just to manually restart what won't start automagically.

-PatP

Replication - Changes to Server databases impact to local database

We have a SQLSERVER database that is replicated to many users.
We are currently in an expansion phase where we need to make changes
to the server database. Each time we rollout a new release, we are
deleting the local replicating database and recreating.

Is there any way to automatically transfer the changes from the server
to existing local database without deleting?dipillama@.nswccd.navy.mil (Michael diPilla) wrote in message news:<4e67e68b.0308181234.4c8e5e98@.posting.google.com>...
> We have a SQLSERVER database that is replicated to many users.
> We are currently in an expansion phase where we need to make changes
> to the server database. Each time we rollout a new release, we are
> deleting the local replicating database and recreating.
> Is there any way to automatically transfer the changes from the server
> to existing local database without deleting?

It's not clear what you mean by 'changes' - changes to table
structures can be replicated if you make them through the publication
properties dialogue.

I'd suggest you post this in microsoft.public.sqlserver.replication,
as you'll probably get a better answer there.

Simon

Replication

I was working on a project that use local and remote SQL server. In order to keep the database up-to-date I wanted to implement replication on the SQL servers. But unfortunately thetransaction replication which meet my requirement best is disabled on the replication configuration module (snapshoot and merge replications are active). Is there any way I can make the transaction replication enabled. I know it was supposed to be enabled by default. I’m using Windows 2003 server and SQL server 2000.

Sincerely

Do you mean you can't select the Transactional Replication as Replication Type when configure Publication?|||Yes, that is what i mean.|||Sorry I haven't heard of such issue. If you have no better choice, you may reinstall the client tools to see whether it helps.

Replication

I have a customer who has Access databases at local sites who wants the data
replicated nightly to MS-SQL Server using broadband connection. I have very
limited knowledge of best practices to accomplish this reliably.

Right now they are using some Java app that exports the Access data then
emails the files as CSV. The emails are then manually taken, copied then
imported. Very cumbersome process and VERY unreliable. There's gotaa be a
better way.

I want to recomend that they contract an expert to set this up but really
can't even say for certian what type of person they should look for at this
point.

Any ideas from a 40,000 foot perspective?

Thanks in advance.

- Ben"Ben" <Sorry@.TooManyViruses.com> wrote in message
news:6Eeic.14065$d7.7176@.twister.rdc-kc.rr.com...
> I have a customer who has Access databases at local sites who wants the
data
> replicated nightly to MS-SQL Server using broadband connection.

Clarification: They want data stored in Access at many sites replicated to a
centralized MS-SQL Database via broadband connections (Cable, DSL, etc.).

> I have very limited knowledge of best practices to accomplish this
reliably.
> Right now they are using some Java app that exports the Access data then
> emails the files as CSV. The emails are then manually taken, copied then
> imported. Very cumbersome process and VERY unreliable. There's gotaa be
a
> better way.
> I want to recomend that they contract an expert to set this up but really
> can't even say for certian what type of person they should look for at
this
> point.
> Any ideas from a 40,000 foot perspective?
> Thanks in advance.
> - Ben|||"Ben" <Sorry@.TooManyViruses.com> wrote in message
news:1Geic.14066$d7.8263@.twister.rdc-kc.rr.com...
> "Ben" <Sorry@.TooManyViruses.com> wrote in message
> news:6Eeic.14065$d7.7176@.twister.rdc-kc.rr.com...
> > I have a customer who has Access databases at local sites who wants the
> data
> > replicated nightly to MS-SQL Server using broadband connection.
> Clarification: They want data stored in Access at many sites replicated to
a
> centralized MS-SQL Database via broadband connections (Cable, DSL, etc.).
> > I have very limited knowledge of best practices to accomplish this
> reliably.
> > Right now they are using some Java app that exports the Access data then
> > emails the files as CSV. The emails are then manually taken, copied
then
> > imported. Very cumbersome process and VERY unreliable. There's gotaa
be
> a
> > better way.
> > I want to recomend that they contract an expert to set this up but
really
> > can't even say for certian what type of person they should look for at
> this
> > point.
> > Any ideas from a 40,000 foot perspective?
> > Thanks in advance.
> > - Ben

You might want to post in microsoft.public.sqlserver.replication for more
information, but I believe that Access is only supported as a subscriber
(receives data) not a publisher (sends data).

Alternatives would include setting up linked servers to the Access
databases, and pulling in the data with direct SELECT queries. Or use DTS to
create a generic data transfer package, which is parameterized based on the
Access DB location.

See "sp_addlinkedserver" and "Heterogeneous Subscribers" in Books Online for
more information.

Simon|||"Simon Hayes" <sql@.hayes.ch> wrote in message
news:4089b32d_2@.news.bluewin.ch...
> "Ben" <Sorry@.TooManyViruses.com> wrote in message
> news:1Geic.14066$d7.8263@.twister.rdc-kc.rr.com...
> > "Ben" <Sorry@.TooManyViruses.com> wrote in message
> > news:6Eeic.14065$d7.7176@.twister.rdc-kc.rr.com...
> > > I have a customer who has Access databases at local sites who wants
the
> > data
> > > replicated nightly to MS-SQL Server using broadband connection.
> > Clarification: They want data stored in Access at many sites replicated
to
> a
> > centralized MS-SQL Database via broadband connections (Cable, DSL,
etc.).
> > > I have very limited knowledge of best practices to accomplish this
> > reliably.
> > > > Right now they are using some Java app that exports the Access data
then
> > > emails the files as CSV. The emails are then manually taken, copied
> then
> > > imported. Very cumbersome process and VERY unreliable. There's gotaa
> be
> > a
> > > better way.
> > > > I want to recomend that they contract an expert to set this up but
> really
> > > can't even say for certian what type of person they should look for at
> > this
> > > point.
> > > > Any ideas from a 40,000 foot perspective?
> > > > Thanks in advance.
> > > > - Ben
> > > You might want to post in microsoft.public.sqlserver.replication for more
> information, but I believe that Access is only supported as a subscriber
> (receives data) not a publisher (sends data).
> Alternatives would include setting up linked servers to the Access
> databases, and pulling in the data with direct SELECT queries. Or use DTS
to
> create a generic data transfer package, which is parameterized based on
the
> Access DB location.
> See "sp_addlinkedserver" and "Heterogeneous Subscribers" in Books Online
for
> more information.
> Simon

Thanks for the leads.

Replication

I have a customer who has Access databases at local sites who wants the data
replicated nightly to MS-SQL Server using broadband connection. I have very
limited knowledge of best practices to accomplish this reliably.

Right now they are using some Java app that exports the Access data then
emails the files as CSV. The emails are then manually taken, copied then
imported. Very cumbersome process and VERY unreliable. There's gotaa be a
better way.

I want to recomend that they contract an expert to set this up but really
can't even say for certian what type of person they should look for at this
point.

Any ideas from a 40,000 foot perspective?

Thanks in advance.

- Ben"Ben" <Sorry@.TooManyViruses.com> wrote in message
news:6Eeic.14065$d7.7176@.twister.rdc-kc.rr.com...
> I have a customer who has Access databases at local sites who wants the
data
> replicated nightly to MS-SQL Server using broadband connection.

Clarification: They want data stored in Access at many sites replicated to a
centralized MS-SQL Database via broadband connections (Cable, DSL, etc.).

> I have very limited knowledge of best practices to accomplish this
reliably.
> Right now they are using some Java app that exports the Access data then
> emails the files as CSV. The emails are then manually taken, copied then
> imported. Very cumbersome process and VERY unreliable. There's gotaa be
a
> better way.
> I want to recomend that they contract an expert to set this up but really
> can't even say for certian what type of person they should look for at
this
> point.
> Any ideas from a 40,000 foot perspective?
> Thanks in advance.
> - Ben|||"Ben" <Sorry@.TooManyViruses.com> wrote in message
news:1Geic.14066$d7.8263@.twister.rdc-kc.rr.com...
> "Ben" <Sorry@.TooManyViruses.com> wrote in message
> news:6Eeic.14065$d7.7176@.twister.rdc-kc.rr.com...
> > I have a customer who has Access databases at local sites who wants the
> data
> > replicated nightly to MS-SQL Server using broadband connection.
> Clarification: They want data stored in Access at many sites replicated to
a
> centralized MS-SQL Database via broadband connections (Cable, DSL, etc.).
> > I have very limited knowledge of best practices to accomplish this
> reliably.
> > Right now they are using some Java app that exports the Access data then
> > emails the files as CSV. The emails are then manually taken, copied
then
> > imported. Very cumbersome process and VERY unreliable. There's gotaa
be
> a
> > better way.
> > I want to recomend that they contract an expert to set this up but
really
> > can't even say for certian what type of person they should look for at
> this
> > point.
> > Any ideas from a 40,000 foot perspective?
> > Thanks in advance.
> > - Ben

You might want to post in microsoft.public.sqlserver.replication for more
information, but I believe that Access is only supported as a subscriber
(receives data) not a publisher (sends data).

Alternatives would include setting up linked servers to the Access
databases, and pulling in the data with direct SELECT queries. Or use DTS to
create a generic data transfer package, which is parameterized based on the
Access DB location.

See "sp_addlinkedserver" and "Heterogeneous Subscribers" in Books Online for
more information.

Simon|||"Simon Hayes" <sql@.hayes.ch> wrote in message
news:4089b32d_2@.news.bluewin.ch...
> "Ben" <Sorry@.TooManyViruses.com> wrote in message
> news:1Geic.14066$d7.8263@.twister.rdc-kc.rr.com...
> > "Ben" <Sorry@.TooManyViruses.com> wrote in message
> > news:6Eeic.14065$d7.7176@.twister.rdc-kc.rr.com...
> > > I have a customer who has Access databases at local sites who wants
the
> > data
> > > replicated nightly to MS-SQL Server using broadband connection.
> > Clarification: They want data stored in Access at many sites replicated
to
> a
> > centralized MS-SQL Database via broadband connections (Cable, DSL,
etc.).
> > > I have very limited knowledge of best practices to accomplish this
> > reliably.
> > > > Right now they are using some Java app that exports the Access data
then
> > > emails the files as CSV. The emails are then manually taken, copied
> then
> > > imported. Very cumbersome process and VERY unreliable. There's gotaa
> be
> > a
> > > better way.
> > > > I want to recomend that they contract an expert to set this up but
> really
> > > can't even say for certian what type of person they should look for at
> > this
> > > point.
> > > > Any ideas from a 40,000 foot perspective?
> > > > Thanks in advance.
> > > > - Ben
> > > You might want to post in microsoft.public.sqlserver.replication for more
> information, but I believe that Access is only supported as a subscriber
> (receives data) not a publisher (sends data).
> Alternatives would include setting up linked servers to the Access
> databases, and pulling in the data with direct SELECT queries. Or use DTS
to
> create a generic data transfer package, which is parameterized based on
the
> Access DB location.
> See "sp_addlinkedserver" and "Heterogeneous Subscribers" in Books Online
for
> more information.
> Simon

Thanks for the leads.|||I have more than 7 years of Experience with Replication if you want I can
Help u out in this. Please email me nehapatel75@.yahoo.com