Simon,

>Not quite sure the full scope of this thread, but do be very careful to ensure that this SQL Server has been protected against the Slammer virus and is patched properly.
>
>It should also be listening on some port other than the default 1433/1434.

Good points to mention for the historical record. I should point out as well that what I'm setting up with my hosting company is ONLY for fake test data which I don't really care about. If this was REAL data, I'm fairly certain I could only make it secure as a dedicated server (mine or theirs) which would give me the flexibility for to properly set security. But I can do this for like $8/month. I don't think the economics make sense for a hosting company to try to setup a useable, shared, secure SQL Server server.

The recommended security setup would be a very interesting thread as well, but well beyond the scope of my current problems.