Called web page from DTS

How can I execute or access a web page from a DTS package?

Both SQL server AND website are hosted on the same server (a Dual 2.4Gz Xeon with 2Gb RAM, RAID 5 etc)

I have 2 tables in SQL server 2000 that hold orders. These need to be posted into another table at a predefined time (ie: 4:30pm) and at the same time, access a remote address (a web service) and post certain elements of the order back.

Basically, can anyone help me out on how to execute a web page from a DTS.

I do NOT want to access a DTS from a webpage, which is all I'm finding at the moment.Not a problem - solved my problem|||How did you solve your problem? Did you use the ServerHTTP object through VBScript?

David|||Create stored proc with :

exec xp_cmdshell 'c:\temp\test.vbs

Call stored proc from DTS

test.vbs should contain something like:

Set WshShell = WScript.CreateObject("WScript.Shell")
WshShell.Run("http://localhost/yoursite/yourpage.aspx")

and then do whatever you like in 'yourpage.aspx'

Works fine for me, but then I have full control over the server. If the site is hosted with a hosting company you may have problems using xp_cmdshell due to the fact that it can pose a security problem because it can pretty much perform any command on the server.|||Why did you create the stored proc, and why did you create the vbs file? Why not just execute the vbscript within the DTS package itself?|||Note: I didn't post ALL of my code for the stored proc - I only posted the relevent part of it.

There's a lot more going on in the procedure which I haven't mentioned, which I didn't want to post.

Calculations for number of DB's on a SQL Server 2000 server

Is there a Microsoft recommendation for how many databases that can exist on
a SQL Server 2000 (std ed) server (Windows 2000 4 CPU, 4GB RAM)? What form
ulas/calculations can be made to determine the capacity (# of db's w/o affec
ting performance/resources)
for a given server?It's not so much the number of databases that matter as much as their usage.
We have a 2 CPU box with 2 Gb of RAM that has 107 databases on it and works
great. We also have a 4CPU box with 8Gb of RAM with 67 databases on it that
works fine. We then have a 4CPU cluster with 4 Gb of RAM that has only 3
databases, the application runs fine but our database box is about maxed
out.
Basically other than disk space, a database won't consume SQL Server
resources unless it's actually used. So apart from the fixed limitation of
32,767 databases per instance there is no concern about the number of
databases. It's all about their utilization.
"LAM" <anonymous@.discussions.microsoft.com> wrote in message
news:2F6DFF19-F6B1-446A-85FA-0BDA53230CF1@.microsoft.com...
> Is there a Microsoft recommendation for how many databases that can exist
on a SQL Server 2000 (std ed) server (Windows 2000 4 CPU, 4GB RAM)? What
formulas/calculations can be made to determine the capacity (# of db's w/o
affecting performance/resources) for a given server?

Calculations for number of DB's on a SQL Server 2000 server

Is there a Microsoft recommendation for how many databases that can exist on a SQL Server 2000 (std ed) server (Windows 2000 4 CPU, 4GB RAM)? What formulas/calculations can be made to determine the capacity (# of db's w/o affecting performance/resources) for a given server?It's not so much the number of databases that matter as much as their usage.
We have a 2 CPU box with 2 Gb of RAM that has 107 databases on it and works
great. We also have a 4CPU box with 8Gb of RAM with 67 databases on it that
works fine. We then have a 4CPU cluster with 4 Gb of RAM that has only 3
databases, the application runs fine but our database box is about maxed
out.
Basically other than disk space, a database won't consume SQL Server
resources unless it's actually used. So apart from the fixed limitation of
32,767 databases per instance there is no concern about the number of
databases. It's all about their utilization.
"LAM" <anonymous@.discussions.microsoft.com> wrote in message
news:2F6DFF19-F6B1-446A-85FA-0BDA53230CF1@.microsoft.com...
> Is there a Microsoft recommendation for how many databases that can exist
on a SQL Server 2000 (std ed) server (Windows 2000 4 CPU, 4GB RAM)? What
formulas/calculations can be made to determine the capacity (# of db's w/o
affecting performance/resources) for a given server?

Calculations for number of DB's on a SQL Server 2000 server

Is there a Microsoft recommendation for how many databases that can exist on a SQL Server 2000 (std ed) server (Windows 2000 4 CPU, 4GB RAM)? What formulas/calculations can be made to determine the capacity (# of db's w/o affecting performance/resources)
for a given server?
It's not so much the number of databases that matter as much as their usage.
We have a 2 CPU box with 2 Gb of RAM that has 107 databases on it and works
great. We also have a 4CPU box with 8Gb of RAM with 67 databases on it that
works fine. We then have a 4CPU cluster with 4 Gb of RAM that has only 3
databases, the application runs fine but our database box is about maxed
out.
Basically other than disk space, a database won't consume SQL Server
resources unless it's actually used. So apart from the fixed limitation of
32,767 databases per instance there is no concern about the number of
databases. It's all about their utilization.
"LAM" <anonymous@.discussions.microsoft.com> wrote in message
news:2F6DFF19-F6B1-446A-85FA-0BDA53230CF1@.microsoft.com...
> Is there a Microsoft recommendation for how many databases that can exist
on a SQL Server 2000 (std ed) server (Windows 2000 4 CPU, 4GB RAM)? What
formulas/calculations can be made to determine the capacity (# of db's w/o
affecting performance/resources) for a given server?