We deploy fat clients across the internet which currently connect thru RDS

to an SQL server box at our main office.  Today my boss asked why we don't

just use SQL's native driver since you get to specify the server there.  



I couldn't answer because I'd forgotten :-)



I'm sure we had a good reason for using RDS rather than SQL's native

drivers.  Anyone got suggestions?



Ta.

Hi Steve



Try it and you'll find out why (eventually)..



There's the speed issue and also you will be connecting people to your

SQLServer box for longer periods rather than using connections on the IIS

server that allows your RDS access and hence allows connection pooling

server side.



Stick with RDS!



HTH



David Billingham





----- Original Message -----

From: "Steve Carter" <Steve.Carter@t...>

To: "ASP_ADO_RDS" <asp_ado_rds@p...>

Sent: Monday, October 08, 2001 10:32 AM

Subject: [asp_ado_rds] Why RDS? Why not connect using SQL's own driver?





> We deploy fat clients across the internet which currently connect thru RDS

> to an SQL server box at our main office.  Today my boss asked why we don't

> just use SQL's native driver since you get to specify the server there.

>

> I couldn't answer because I'd forgotten :-)

>

> I'm sure we had a good reason for using RDS rather than SQL's native

> drivers.  Anyone got suggestions?

>

> Ta.