I did have a proviso in my post that my main production experience with Replication is with MSSQL 2000, but I deleted it for the sake of brevity. However, I'm...

Nice succinct answer, thanks Steve.

Just one additional question - at what point woud you consider splitting the data into secondary data files (and filegroups), and moving these filegroups onto separate...

Thanks for the link, an easy read but it explains some complex technologies. I wish I'd come across it a few months back.

Transactional Replication could be a more suitable solution to provide a reporting-only database.

However, I think in this case TCP Ports will be a big issue. It's already mentioned that the...

.NET 2.0 will certainly install on Windows 2000 without affecting your SQL Server. Not so sure about GDI+, but it is only an API, so shouldn't have any...

Agreed, I don't think you can use the built-in tools for Log Shipping (the secondary server instance and database must be visible to the primary database).

You probably need to do...

Perhaps the esteemed Mr Phil Factor would like to get involved in the discussion?

I was only regurgitating what...

Yes, I agree, good concise advice.

Just one quick question - you mention the Fill Factor defaults to 100% in 2005, whereas it was 90% in 2000. [To be precise, it...

I agree, an interesting discussion on using more than 4GB of RAM with 32bit hardware. Couple of points I would like to add/clarify:

No application references memory directly; all applications makes...

Thanks for kicking this off, a good topic for real-world situations.

My first comment is on your standard 8-disk setup - have you considered the capabilities of your hardware RAID...

MsDtsServer is the DCOM application name for: Microsoft.SqlServer.Dts.Server.DtsServer

better known to its friends as CLSID ABF05265-635E-44B0-A28F-AEA45247ACA0

You can discover this by searching for the CLSID in the registry.

I have a similar permissions...

Could you post the full Event IDs and related info for the errors you received?

Andy

Perhaps you could be a little more specific? What, exactly, is not working? What steps have you taken to figure out what is wrong?

Is the long copy-and-paste...

A quick read through the (overly-long) notes tells me that you are trying to create ALL the endpoints on TCP/4040.

That is fine if each MSSQL Instance is on a separate...