BigSam, I remember reading somewhere that the Distributor should be same or higher version than the Publisher or the subscriber. I am not sure if that is your issue.

This thread is going to get interesting. :hehe:

Sessions or Cache might work for you in this case. You could look at Third Party caching tools like memcache as well.

I would go for option 1. It is just a friendly warning saying that your company details are out and you took care of it for now. But to keep...

If you want to follow GSquared advice, I would advice to read up on Table partitioning first. There is a very good white paper on Table partitioning for SQL 2008...

That was a pretty strong reply.... 🙂

Hope he learns...

I am not sure..I have a feeling that he is being sarcastic... But I am going to leave it as it is... 🙂

Am I being too rude here?

I am sure you have a SQL Server right in front of you. Why not try it out. Also check BOL. You should be able to get enough info there...

And what the heck is this?:crazy:

It will always be an ongoing battle...:-)

It is probably the distributor trying to get the data from the snapshot directory. Usually everyone specifies a shared path for the Snapshot.

You can specify that you do not want delete to propagate to the Subscribers. That would probably mean that even if there is a real that had to be done,...

Jeffrey Williams-493691 (1/29/2010)

Well Roy - you might want to slap yourself...

"Slap myself in on my forehead" Forgot that you cannot connect from SSMS 2005 to SQL 2008 DB