January 3, 2012 at 3:36 pm
I need to know if it is possible and if so seek docs, tuts and advice on how to git er' done.
I have a website on HostServerA that I need to migrate to HostServerB but at this time I can't afford the SQL Server add-on fee from HostServerB.
The website uses ASP.NET Membership that currently runs with on SQL Server 2008 at HostServerA. If I migrate the website to HostServerB what if anything can I do to use the SQL Server 2008 database at HostServerA to authenticate users, store data and so on?
I have until Friday Jan. 6th to learn if this is possible. Please help me have a Happy New Year lol
January 3, 2012 at 3:43 pm
Are you dealing with a hosting provider? If so, you'll need to talk to them. You won't have access to the tools you'll need.
If not, you rarely (preferably never) run the db server on the same physical/virtual as the website. This shouldn't be a problem. Just have the site login to the db server as a user (most likely via odbc) and you'll need to setup some basic security.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
January 3, 2012 at 4:50 pm
Thanks Craig.
Yes, I'm trying to cope with a now arrogant ripoff hosting provider WebHost4Life (HostServerA) that has refused to update ASP.NET for the past 21 months after being acquired by Endurance International which is on their second or third business name because they are actually "holding company scum" that has entered our line of business and has literally been cheating and ripping off tens of thousands of customers after acquiring the hosting companies they acquire.
I can access and modify the database on HostingServerA server using VisualStudio Server Explorer running on my local machine so not having the experience in this context I thought it shoud be possible to simply have a connection string on website running on HostServerB do the same thing.
I also have SQL Management Studio 2008. What's still lacking is the experience in this context so could you refer to docs, blogs, tuts or whatever?
January 3, 2012 at 5:24 pm
clintonG (1/3/2012)
I can access and modify the database on HostingServerA server using VisualStudio Server Explorer running on my local machine so not having the experience in this context I thought it shoud be possible to simply have a connection string on website running on HostServerB do the same thing.I also have SQL Management Studio 2008. What's still lacking is the experience in this context so could you refer to docs, blogs, tuts or whatever?
Sounds problematic, at least from the provider perspective. This is pretty basic connection string stuff. The problem is how they firewall, amongst other things, internally. If the servers are on different sub-domains or they just don't let them talk you can't force them to.
In theory, on Server B you should simply be able to put in the servername/instancename of the instance you want into your connection string, a SQLUser/Password combination, and be good to go from there. Basically you'd just swap out '(local)' in the connection string with the correct target.
However, if you can't get at their network, you have no idea if that'll even work.
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
January 3, 2012 at 5:37 pm
I agree as I presumed connecting from a remote website with correct connection string should be no different than connecting remotely using Visual Studio or Management Studio --however-- my own firewall has been configured to specifically recognize and allow those client applications as I presume HostServerA configures their firewalls which is not to say requests from some website somewhere must also be granted access.
I was not specific about ports or other details but have asked HostServerA about their "policy" and here is their reply...
"We support remote access to the MS SQL database so we do not block. We provide access only in our server. We do not support remote access in any properties."
So I'm going to get a new account at HostServerB and give it a shot. Thanks for commenting Craig.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply