MS Access to SQL Server

Hello,

I'm trying to get a rather large Access file (I also have it in comma separated format) that I'd like to get into SQL Server. Is there a way I can do this without transferring the data over line by line (it's a 78,000 line file)?

Thanks,
Scott

 

How are you using the Import tool in SQL Server, which version of SQL Server?
By the way, have you tried the Upgrade tool for this within the Access IDE?

I've done this many times and can give you specific details, it's rather straight forward most of the time.
Salute,
Mark Wisecarver

 

Here's a little more detail about my situation:

I have a comma separated file that I'd like to put into the SQL Server 2005 database that discountasp.net is hosting. I have SQL Express on my computer. I could not find a way to turn the .csv file into an SQL file (I've looked several times for an Import tool or something similar but I haven't seen one) so I created an Access file, hoping that moving from Access into SQL would be easier. So far, it hasn't been. And no, I don't have a lot of database experience, so I could be missing something simple.

Since my last post, I found a tool on the Microsoft website that converts Access files into SQL Server files. I was able to connect to the discountasp SQL Server 2005 and import column data to the database file. However, I keep getting errors when I try to move the data itself. The error messages in the program aren't that helpful, but the Event Viewer says 'DCOM was unable to communicate with the computer SQL2K504 using any of the configured protocols.'

Do you have any ideas?

Thanks,
Scott

 

SQL Server does an excellent job importing comma separated CSV files.
I set up stored procedures for Siemens that load CSV files that are kicked out from a huge Oracle system.
With DTS jobs the CSV files are read in with SQL Server SPs whilequalifying for duplicate records.

You can geta full version of SQL Server 2005 for $50 but apparently it won't work with the express version of VS 2005.

If you want me to import the CSV files for you I don't mind helping.
However if you will be doing this often you will want to get the developer edition of SQL Server 2005.
I recently upgraded to the professional version of VS 2005 and am very glad I did.
*Uninstalled my local SQL Server 2000 once SQL Server 2005 had imported the records, no problems at all.
Salute,
Mark Wisecarver