When you create a startup or shutdown service, you must register that service in the package with which it will be used. When you create a replication service, you can register any valid service from any loaded package on the server, including the current package itself.

Because services in a package are not made available to clients until that package's startup services finish executing, you should avoid implementing startup services that access busy remote servers. They will delay the availability of other services in that package.

You may assign one or more startup services to a package; however, you cannot specify the order in which they will execute. If you have a series of operations that must execute in a specific order, encode the entire sequence within a single service or have a startup service invoke others.