Viewing 15 posts - 226 through 240 (of 1,790 total)
Read this before making further decisions.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 21, 2011 at 11:14 am
You could run a trace looking for activity coming from the publisher server / database. Typically, your distribution agent is going to be named PubServer_PubDB_ . You can query sysprocesses...
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 21, 2011 at 10:44 am
At a minimum, when SQL Server is the only application running on the server, I will at least leave 2 GB for the OS and any odd processes, etc. With...
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 14, 2011 at 9:10 pm
I typically force escalation on replication issues due to some of what you describe. I'll leave it at that.
Glad you got it fixed.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 14, 2011 at 8:57 pm
TheLazyWriter (3/11/2011)
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 11, 2011 at 10:12 am
Yes, any reference to that database will have to be changed to the new name; whether in SSIS, query, connection string, etc. Best to log all connections to that database...
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 11, 2011 at 10:07 am
Agree with danT, you should be profiling to find the high read / write queries. Pick a number, say 20,000 reads, and use that as your filter. Find the queries...
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 11, 2011 at 10:00 am
Krasavita (3/11/2011)
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 11, 2011 at 9:43 am
Krasavita - sounds like you should be ok going with MysteryJimbo's recommendation then and that will allow you to avoid the new publication.
Let us know how that goes.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 11, 2011 at 9:28 am
MysteryJimbo (3/11/2011)
David Benoit (3/11/2011)[hr
Correct me if I am wrong but I thought that this was ONLY true when immediate_sync was not set on and if it was it would generate...
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 11, 2011 at 9:27 am
256 GB
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 11, 2011 at 9:05 am
MysteryJimbo (3/11/2011)
Ensure you do this in TSQL....
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 11, 2011 at 8:48 am
There is a way (which I have not tested yet - due to though) to put a table in the same publication and only force the snapshot for that table....
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 11, 2011 at 6:46 am
Validate is only going to look for data consistency - http://msdn.microsoft.com/en-us/library/ms151251.aspx.
If you can reinitialize all the subscriptions then do the first set of steps that I recommended and that...
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 11, 2011 at 6:33 am
Krasavita (3/10/2011)
I do't have access to that server (subscriber)and I don't think it is a good...
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
March 10, 2011 at 2:23 pm
Viewing 15 posts - 226 through 240 (of 1,790 total)