Viewing 15 posts - 46 through 60 (of 221 total)
If the subscriber's database is no longer involved in replication - either as a subscriber or as a publisher - try running sp_removedbreplication at the subscriber.
HTH,
Paul Ibison (SQL Server MVP)
October 21, 2004 at 8:43 am
The simplest solution is Log-Shipping. You could do this out of the box if you have enterprise edition of SQL Server, or using simple scripts from the resource kit if...
September 17, 2004 at 3:59 am
Joe,
neither method can use HTTP. Actually, replication can for CE devices but this is not especially useful for failover . I'm hoping 2005 will...
June 18, 2004 at 9:38 am
Thanks Hans,
I agree that 1 minute is more of a theoretical than practical minimum for log shipping, but it is the MS recommendation in one specific case I know of....
June 17, 2004 at 10:00 am
David - came across this link which might help you: http://communities2.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.replication&tid=40b9388c-7b9d-4f21-b38e-eb8e157886ae&p=5&shell=/communities/newsgroups/en-us/Configuration.xml, regards, Paul
January 29, 2004 at 10:33 am
David,
while I've not seen this particular error before, I wonder if it is due to the edition of SQL Server you are using. I use personal edition at home and...
January 27, 2004 at 2:19 pm
The subscriptions folder shows a union of the subscription metatables in each subscriber database. If you remove a publication before the subscription, orphaned records can be left behind and they...
January 27, 2004 at 2:15 pm
Hi,
The GUI makes supporting it a bit more difficult (opaque) and it is restricted to differently named servers as subscribers (ie no 2 subscribers on the same server) but I've...
January 27, 2004 at 2:11 pm
The profiles for each subscriber's agent are often used for optimisation, but this will not reduce the volume of data to be moved form your publisher to the subscribers. In...
January 25, 2004 at 1:04 pm
Hi,
strictly speaking, subscriptions are per publication, not per article, so the simple answer is no - using standard techniques. However, I have partitioned data according to subscriber using the integration...
January 25, 2004 at 12:59 pm
Hi,
not having seen this particular error for replication itself before, and given that the topology was
working correctly previously, my guess is a connectivity issue - eg network card problems....
January 25, 2004 at 12:55 pm
Hi,
probably need a bit more info on this one (any other error log info?) - also what is OSQL trying to do - are you using dynamic script execution, or...
January 25, 2004 at 12:51 pm
Hi,
the replication merge agent has a parameter - HOSTNAME - which can be added to the job and configured accordingly.
HTH,
Paul
ps a few more details on http://www.replicationanswers.com (merge section)
January 25, 2004 at 12:46 pm
I'm not suggesting it, but if you did want to go down this route, you could more easily run "Alter database single_user with rollback immediate".
Paul Ibison
April 24, 2003 at 1:42 pm
Yes - the bulk load com interface is in sqlxml 3.0 sp1 which is free to download. As far as I know there's no intrinsic support in DTS although the...
April 16, 2003 at 5:07 am
Viewing 15 posts - 46 through 60 (of 221 total)