GoDaddy SQL Web Admin -- Importing CSV file

Okay -- Frustrated... any guideance appreciated.
Our website is currently using an MS-ACCESS file for it's back end
database. Hosted on GoDaddy. Due to performance issues, we are
switching over to GoDaddy's MS-SQL Server. Our only management tool is
the SQL WEB ADMIN.
The only way we can see to import data into a table is through
importing a csv. THIS IS FINE!
We went to access, and exported the tables, using a comma delimited,
text identiffier of quotes, and imported it into sql through the SQL
WEB ADMIN.
EXCEPT -- all the text fields physically kept the quotes.
A field that previously contained: Hello kitty, how are you
Now contains "Hello kitty, how are you"
We have several long descriptions and text fields that contain commas
and semi-colons so we definately need a text identifier. So how do we
export the file from access and successfully import it into our godaddy
hosted SQL server using ms SQL WEB ADMIN?
Any help, guidance, comments would be greatly appreciated.
Don O
Palm Springs, CA
president@.palmspringsbears.org
You can use DTS package to migrate data from MS ACCESS to direct SQL Server
without exporting to csv.
-MB
"BigDesert" <doldenburg@.bigdesert.net> wrote in message
news:1167600961.063396.234590@.n51g2000cwc.googlegr oups.com...
> Okay -- Frustrated... any guideance appreciated.
> Our website is currently using an MS-ACCESS file for it's back end
> database. Hosted on GoDaddy. Due to performance issues, we are
> switching over to GoDaddy's MS-SQL Server. Our only management tool is
> the SQL WEB ADMIN.
> The only way we can see to import data into a table is through
> importing a csv. THIS IS FINE!
> We went to access, and exported the tables, using a comma delimited,
> text identiffier of quotes, and imported it into sql through the SQL
> WEB ADMIN.
> EXCEPT -- all the text fields physically kept the quotes.
> A field that previously contained: Hello kitty, how are you
> Now contains "Hello kitty, how are you"
> We have several long descriptions and text fields that contain commas
> and semi-colons so we definately need a text identifier. So how do we
> export the file from access and successfully import it into our godaddy
> hosted SQL server using ms SQL WEB ADMIN?
> Any help, guidance, comments would be greatly appreciated.
> Don O
> Palm Springs, CA
> president@.palmspringsbears.org
>
|||I don't use sql web admin so can't really help much there.
However, if you have access to a sql client tool like Query Analyzer, you
can read data from Access (via opendatasource or openrowset) and insert it
directly into sqlserver table.
e.g.
INSERT into SqlTable
SELECT *
FROM OpenDataSource( 'Microsoft.Jet.OLEDB.4.0',
'Data Source="x:\godaddy\myAccess.mdb";User
ID=Admin;Password=;')...myAccessTable
INSERT into SqlTable
SELECT *
FROM OPENROWSET('Microsoft.Jet.OLEDB.4.0',
x:\godaddy\myAccess.xls.mdb';'admin';'', myAccessTable) as x
-oj
"BigDesert" <doldenburg@.bigdesert.net> wrote in message
news:1167600961.063396.234590@.n51g2000cwc.googlegr oups.com...
> Okay -- Frustrated... any guideance appreciated.
> Our website is currently using an MS-ACCESS file for it's back end
> database. Hosted on GoDaddy. Due to performance issues, we are
> switching over to GoDaddy's MS-SQL Server. Our only management tool is
> the SQL WEB ADMIN.
> The only way we can see to import data into a table is through
> importing a csv. THIS IS FINE!
> We went to access, and exported the tables, using a comma delimited,
> text identiffier of quotes, and imported it into sql through the SQL
> WEB ADMIN.
> EXCEPT -- all the text fields physically kept the quotes.
> A field that previously contained: Hello kitty, how are you
> Now contains "Hello kitty, how are you"
> We have several long descriptions and text fields that contain commas
> and semi-colons so we definately need a text identifier. So how do we
> export the file from access and successfully import it into our godaddy
> hosted SQL server using ms SQL WEB ADMIN?
> Any help, guidance, comments would be greatly appreciated.
> Don O
> Palm Springs, CA
> president@.palmspringsbears.org
>
|||Don O,
I just got off the phone with GoDaddy. They are telling me that what you are trying to do won't work on their servers~ I am trying to do the same thing.
Have you gotten yours to work yet?
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
|||Frankly, I'm not surprised. What you folks want to do amounts to sitting
at the keyboard of their server and having at it...
Regards,
Hank Arnold
Angie D wrote:
> Don O,
> I just got off the phone with GoDaddy. They are telling me that what you are trying to do won't work on their servers~ I am trying to do the same thing.
> Have you gotten yours to work yet?
>
> EggHeadCafe.com - .NET Developer Portal of Choice
> http://www.eggheadcafe.com

Godaddy server/SQL Management studio connection question

Hello,

I just got a personal site with godaddy that I would like to be able to connect to using SQL Server management studio

I try to connection using

Server Name: sdhfuh928323984ujf.phx3.secureserver.net

authentication: sql server

Username: my username

password: my password

Then it tries to connect and gives me an error that I can't and remote connections may not be allowed.

I followed the directions it gave and turned on remote connections, restarted the server, but I still get the error.

any ideas?

It might be a firewall issue.

GoDaddy + SQL Connection String

I know this has to be answered somewhere, I just need to know, am I going crazy. I have a shared webhost account at Godaddy. My web config was working at one point, but now I am getting this error:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

Now, If I were to look at this, its telling me that it cannot locate the server I am trying to connect to. Below is my connection string and the address I am getting this from is in my information at godaddy. Tell me, is there something that I am doing wrong here?

<connectionStrings>

<addname="Personal"connectionString="Server=whsql-v20.prod.mesa1.secureserver.net;Database=azwd30;User ID=XXXXX;Password=XXXXX;Trusted_Connection=False"providerName="System.Data.SqlClient" />

<removename="LocalSqlServer"/>

<addname="LocalSqlServer"connectionString="Server=whsql-v20.prod.mesa1.secureserver.net;Database=azwd30;User ID=XXXX;Password=XXXXX;Trusted_Connection=False"providerName="System.Data.SqlClient" />

</connectionStrings>

With the same user name and password, I can access the database through Godaddy's site and see my records, and the address 'whsql-v20.prod.mesa1.secureserver.net' is the same as whats on Godaddy's SQL configuration page, the database name is the same, I have double, triple and spent hours checking all that could affect this... I may just be burnt out using Godaddy. It seems I fix one thing, then there is another thing, I fix that, then there is another. I talk to support, and they say, they dont support anything that they have in their sales page for what they offer. I'd rather get support to say somthing like: "You may want to go to google and press the I'm feeling Lucky button. It would be probably be faster and cheaper than using our department, or you can upgrade to our virtual server and have a little more control, not total control but a little more ... what do you say mr Chris?"

Well, I feel almost a little better venting here. Since I have been with GoDaddy, and I live in the same city where they host their servers, I have been in shambles wondering how they can offer all that they do in their sales pitch and then drop a ball and say, we dont support 90% of what you read in the beginning. It almost wants to make you put a huge NoDaddy.com sticker in your back window and drive around town all day in gas with the same money you give to them. Ok, now I am done venting, any Idea's anyone.?

1) Try this maybe?

connectionString="Data Source=whsql-v20.prod.mesa1.secureserver.net;Initial Catalog=azwd30;User ID=XXXX;Password=XXXXX;Persist Security Info=True;Trusted_Connection=True"

2) It has been a long time since i have used a shared hosting environment but I am unable to ping your SQL server. Maybe your server name is wrong? or maybe I wouldnt be able to see it from outside their network... If you are looking at a help page, that server name might just be GenericSampleFAQ-Server01. The actual name of your SQL is probably in an email they sent you.

|||

Thank you for your help, I really appreciate it. You are the man !!!

GoDaddy / MySQL / SQL Server

I don't know if this is unique to GoDaddy: I found the program for working with a MySQL database very intuitive (to the point of compliments). Today I started work with ASP.NET and SQL, and when I went to work with SQL Server (on GoDaddy), it wasn't intuitive, and there was almost nothing on which to click. By chance might there be a tutorial that would help a person who needs to work with SQL Server on a provider like GoDaddy?

This may help...

http://forums.asp.net/thread/1456464.aspx

|||

I'm going through it, and I come to a point where I think it asks me to connect to the server (IP and PORT). I believe GoDaddy doesn't allow this (if someone reads this and I've misinterpreted it, please hollar--I know there is something that GoDaddy forbids regarding connected outside of their system).

If the above is true, does that make it so that the above process won't work (that's what I'm thinking right now.

However, thank you for the above link, because it gave me an idea. GoDaddy has it so that you can run queries. If I had a database with 250 entries and I didn't want to retype them all, I might be able to construct the database through the query box. Thanks! (going to test that out now.)

|||

The thread was started as a request by a newbie for help for someone who is on GoDaddy and they got to the SQL Server, and then they were stuck (what do I do next?) Over time I figured it out, and if you came to this post because you are "stuck", feel free to continue the thread with another question. I'm putting some basic things you want to know below:

Assuming that you've created a database under SQL Server and given it name and a password, and that you clicked on "Open Manager" in the row with the name of your database are now on a page with a name likehttps://mssqladmin.secureserver.net:

You see Quick Help with a bunch of words and icons (this doesn't help you though, those are not links, those are things you will see later).

On the left, you see Connection and Preferences, click Connection. Click the new link 'connection' the comes up underneath.

Put in your user name and password and click Connect.

There should be a new choice between Connection and Preferences on the left and it may have a name like whsql-v03.

Click that. You should then see Databases and Tools, and both will be helpful. Click Tools and then Query Analyser. This box is where you can type a query line that creates a table for your database:

CREATE TABLE mydictionary (word nvarchar(50), definition text)

and if it creates successfully, you will see "The command(s) completed successfully." appear underneath. You now have a table with two fields, word and definition.

Go back to the menu on the left and click Databases. something like DB_123456 comes up and click on that. Underneath you have Tables, Views, Stored Procedures. Click Tables. A list of tables comes up, many that you didn't make, but look for yours at the bottom. Don't click it just yet--instead, mouse over to all the icons on the right in the same row, and click the first one, content.

Look for the word Actions and then click that yellow star/asterisk. The next window gives you text boxes to put in your first entry. Fill them and click Insert.

At this point you have a database. It doesn't have things that are important, like a primary key with auto_increment, but the database will work for the purpose of confirming your first success.

|||

My advice to Godaddy users is to start with getting a simple page working that writes to one table in your new database. That will give you a web.config file with a working database connection and you can move on from there.

The web.config database connection seems a particular issue for newbies, I've put together a page with tips based around going live on GoDaddy with SQL Server, when you've got SQL Express on your local PC.

http://www.salmontraining.com/SqlExpressZone/Articles/why_the_development_config_file_wont_work_on_live_shared_hosting_with_sql_server.aspx