Greg,

The sysjobhistory Table is the one however I see now what you are trying to do! Thats right this table is history only and until a step has completed you...

Can't do! You will have to use a Data Modelling tool such as Microsoft Visio 2002 Enterprise Architect.

You need to find out which query or queries is perfroming poorly! Once you have established that, do an execution plan to see if Indexes are been used. This is...

The MSDB Database contains history about every job. Haven't got time to find out which system table it is in, but have a look in MSDB and try and suss...

How on earth do you expect to retain permissions when you DROP a table? SQL Server isn't some magical toy that can pull a rabit out of a hat!

Think...

Check to see if the 'Distributor_admin' account is used in a Remote Server connection.

If the growth will be 10%/year, then I would place a FILLFACTOR of 90%. This will allow 10% free space on the data/index pages.

SQL Server Services HAVE to be started with a Domain Account not local system account if you want replication to work.

Definitley Merge Replication!

You can use either Replication or just simply restore the Database to another SQL Server. This all depeneds on how up to date you want the copy. If it's real...

For a Database of that size you are better off doing the snapshot manually!

Backup the Database ship it out to your subscribers, attache the database on the subscriber and then...

How are you trying to disable Transactional Replication?

In order to Implement Replication, you have to have the same Database Design/Structure both at the Publisher and Subscriber!.

When you create your Publication, go to the properties of the Article and select the Snapshot tab. From there choose the option "keep the existing table unchanged". By doing this,...

I've never had a problem with sp_repladdcolumn!

As for adding a new table to the replication process, you will have to add it to the publication and either redo the snapshot...