From what I saw it looks like Microsoft updated all supported versions of SQL server at the same time, so the real secret was just getting to either a service...

Hi,

I found the solution. It turns out that our publisher was running the most recent SP2 update for SQL 2008 R2 but the distributor and subscriber were only running...

I found this article which appears will provide what I need:

http://msdn.microsoft.com/en-us/library/ms152560(v=sql.105).aspx

has anyone had any experience with this process and know of anything I should watch out for?

I forgot to mention, I know this is referring to SQL Server 2005, but we are running our publisher as 2008 R2 (enterprise/processor) and subscriber/distributor as 2008 (standard/CAL) and a...

Thanks, Unfortunately, I don't think that will help us out much though. Initializing the subscription isn't that bad, but after the subscription is initialized, we have a process to...

Rebuilding is an option, just our last option. We rebuild our test replication on a regular basis, so the entire process is very well documented. I'm just not...

Doing some more digging online, it sounds like if I back up the master, MSDB and published databases (the distributor is on a different server) and restore them with replication...

The question is sort-of tricky. the real answer is "Indirectly" there are tricks to use rand() when you normally shouldn't be able to...

I've been using case a lot in selectively aggregating to optimize (and simplify) complex reports so the first thing that came to mind for me was something similar to this...

Well, it probably wasn't the best way to handle this, but I came up with a way that actually simplifies the process considerably.  of the 8 possible branches, 6 did...