"kenfine@nospam.nospam" wrote:

>
> I recently signed up for shared web hosting with a commercial hosting
> service (GoDaddy.com) and was awed to discover that although a generous SQL
> Server database package is included, there is not an easy way to connect
> ASP.NET web applications to database servers running outside of the host's
> systems. Indeed, many ports are blocked: I think the only open ports are 80
> and 25.
>
> Surely there is some way around this that I could manage in programming
> and/or via infrastructure magic. I'm running SQL Server 2005 on both ends,
> and have total control over the server/db server on my end.
>
> Can someone suggest if there is a viable approach to somehow "wrap" database
> calls in a way that isn't totally slow and a total mess to work with? Does
> the .NET platform anticipate this kind of problem and have anything
> prebuilt?
>
> Thanks for any ideas. The best answer will probably be to have all of my
> apps and database stuff encapsulated on my host, but there's some testing
> that needs to happen between now and final deployment, and I'd prefer to
> have my database wired up for now.
>
> -KF
>
>
>