-1

I'm trying to import two seperate .RPT files into SQL, one is small, one is large. Both have issues with determining where the columns are seperated.

My solution for this was to import the file into access, define the columns and then save it as a txt file.

This worked perfectly.

The problem however is the larger file is 6 gigs and MS Access won't allow me to open it. When trying to change the extension to simply .txt and importing it into SQL, everything comes down under one column (despite there being 10) and there is no way to accurately seperate the data.

Please help!

Tony Toews
  • 7,850
  • 1
  • 22
  • 27
twrehl
  • 1
  • 1
  • 1
  • What kind of file is a .RPT file? Access has a 2 Gb limit on database file size so it's quite understandable it couldn't import the data. – Tony Toews Jul 21 '11 at 05:20
  • I posted the steps needed to load a .rpt file to SQL Server (or another database) here: https://stackoverflow.com/a/56188149/5070440 – GregGalloway May 17 '19 at 14:09

2 Answers2

0

If the file has column delimiters or fixed column widths you can try the following in SQL Management Studio:

Right click on a database, select "Tasks" and then "Import data...". This will take you through a wizard where you can define the source columns and map them to an existing or new table.

Veldmuis
  • 4,678
  • 4
  • 25
  • 25
0

As Tony stated Access has a hard 2GB limit on database size.

You don't say what kind of file the .RPT file is. If it is a text file, then you could break it into smaller chunks by reading it line by line and appending it into temporary files. Then import/export these smaller files one at a time.

Keep in mind the 2GB limit is on the Access database, so your temporary text files will need to be somewhat smaller because the import will likely introduce some additional overhead. Also, you may need to compact/repair the database in between import/export cycles to reclaim space in the database; simply deleting the records is not enough.

mwolfe02
  • 23,787
  • 9
  • 91
  • 161