[REPL] server config for distributor server?

We are going to have two SQL 2000 Servers with a SQL 2005 distributor server that will handle 1 way transactional replication. What kind of server should I ask IT to spec out that would satisfy an installation such as this?

Our production DB is 30GB and we are replication about 60% of the data to another server.rack mountable
dual processor with hyperthreading
100 GB RAID (disk space is not that important, but might as well make it RAID)
16 GB Memory (from what I understand memory is the most important attribute)

any other suggestions...?

[Expired subscription clean up] job failing

Hi,

The "Expired subscription clean up" job at the distributor keeps failing with the following error. Any ideas what it could be?

Message
Executed as user: domain\servicesql. The Distributor has not been installed correctly. [SQLSTATE 42000] (Error 20036). The step failed.

Thanks,
Priyanga

I came accross the following link which provides a workaround to the problem.
Thanks Narayana!

http://vyaskn.tripod.com/sql_server_2005_expired_subscription_cleanup.htm

Cheers,
Priyanga

|||This is a bug in replication for the case where distributor is not configured as publisher, this bug has been fixed and will be available in SQL Server 2005 SP1.|||This did not fix the error, and I'm running SP2 on SQL Server 2005. Any other solutions available? THANKS!

[Expired subscription clean up] job failing

Hi,

The "Expired subscription clean up" job at the distributor keeps failing with the following error. Any ideas what it could be?

Message
Executed as user: domain\servicesql. The Distributor has not been installed correctly. [SQLSTATE 42000] (Error 20036). The step failed.

Thanks,
Priyanga

I came accross the following link which provides a workaround to the problem.
Thanks Narayana!

http://vyaskn.tripod.com/sql_server_2005_expired_subscription_cleanup.htm

Cheers,
Priyanga

|||This is a bug in replication for the case where distributor is not configured as publisher, this bug has been fixed and will be available in SQL Server 2005 SP1.|||This did not fix the error, and I'm running SP2 on SQL Server 2005. Any other solutions available? THANKS!