Last post Oct 08, 2007 03:21 PM by biobot
Aug 17, 2007 08:34 PM|biobot|LINK
Here are my methods used to deploy a database on Go Daddy Windows shared hosting service:
1) using aspnet_regsql.exe -A all -sqlexportonly example.sql -d databaseownername
With that I go to my host and enter the text into a Query Analyzer, but I get an error message stating that "string or binary data will be truncated" (I have tried a shorter name string) If I try to ignore this, the app fails.
2) using SqlPubWiz and again uploading the text to the Query Analyzer.
With that, I get an error from the QA stating that there is a "syntax error near END." Again if I try to ignore this, the app fails.
Some of you may have seen this, or very similar from me already - please excuse my ineptitude!
Thanks in advance for any help offered!
VWD Express 2005 App Publishing
Aug 18, 2007 06:41 AM|SalmonTraining|LINK
1) You can't do it this way - as you're finding out. The aspnet_regsql.exe is an executable that you would need to run from the command line on the host server - you don't get privileges to do so on shared hosting plan.
2). Using the Database Publishing Wizard is the best way. Unfortunately, the Query Analyser GUI has a few glitches when it interprets standard Transact-SQL statements. I've noticed that Go Daddy has upgraded the interface recently and I have less issues
now with running scripts - but sounds like you're tripping over a problem.
Specifically, a known problem with Query Analyser is with the keyword GOTO at the start of a line. Check out this article for a description and work-around of the problem:
If you've looked at the script generated by the Wizard you'll see that it creates your data model step by step. I suggest you run it in sections. In particular, from the error you mention, I think the script is failing on creating a stored procedure. I suggest
you run the script up to the section that starts creating stored procedures (and I just mean copy-and-paste the text up to that point, or split the script into two files). Then run each procedure creation individually to get to your problem. Once you've isolated
what's falling over, post it to the SQL Server forum within forums.asp.net with the specific problem and someone will help you clean up the script (mention it's Go Daddy, there's a few of us who regularly work with that hosting provider and have experienced
Oct 08, 2007 03:21 PM|biobot|LINK
Thank you for responding, and please excuse my slow response - other committments.
I have elected to cancel my Go-Daddy account for the time being, and to confine my efforts to a local machine.
At this point, I'm wondering whether Go-Daddy is really any different than other shared hosting providers? I notice there are thousands of reported issues, but that may be due to its widespread use.
If I go back to them, I will check out the tutorials you've recommended.