Developer Edition is Enterprise Edition in disguise. Best $50 I ever spent! (That's sad isn't it) I believe the only difference between Dev & Ent is the licensing agreement.

My scenario is that I have developed a few SSIS 2008 packages not realizing that they would not run on my production SQL 2005 Server. So, my plan is to...

As a matter of fact, I have the McNight book. In fact I have two of them. A fat one and a skinny one 🙂 (I'm a book junky)....

Great idea, I had not thought of that. This would give me the truly centralize management I've been looking for. Thank you Bru.

I appreciate all the help guys.

So, sounds like I should probably save the replication for a rainy day. Like I said, last time I was in this situation, I wrapped...

I'm begining to think that perhaps Replication is not practical unless the data can be replicated "as is". Is that a fair statement?

My plan is to "pull" once a day. The Distributor would live on the subscriber. I was thinking the same thing, this might be a job for SSIS. I'm pretty...

Thanks. I get that. The thing is, the data really wasn't designed with replication in mind. The primary keys are "int identitiies" on the publishers. What I really need is...

Awesome, thanks Steve. I'm feeling much better about this adventure having heard that vote of confidence from "The Man"!

One more question. The one thing I'm having trouble...

Interesting idea. I should have thought of that! I think I'm going to try the C# / CLR thing first.

Yea, I know, but unfortunately, I inherited a pretty screwed up environment where the SQL Server basically lives in a "domainless" environment, so I'm pretty much stuck with hacks.

Yea, the CLR was my next stop. I haven't tried that yet. Can the CLR play outside the SQL sandbox?

I've probably answered my own question. Looks to me like it's due to the fact that SS 2005 is running under "LocalSystem", and LocalSystem really cannot see the outside world....

You are right my friend. THANK YOU!

That makes NO sense to me though. I've got in the habit of using varchar(max) for building sql strings since I never know...

Here's some psuedo code of what I'm doing

set @SqlTxt = 'select SomeCol from SomeTable'

select SvrName from syssevers

while SvrName is not null

begin

exec(@SqlTxt) AT [SvrName]

...