December 14, 2004 at 1:15 pm
From Enterprise Manager i am attempting to import some tab delimited data in a .dat file.
I selected my database, right clicked in the right pane and went to all tasks -> Import Data and followed the wizard. Under Data Source Dropdown i chose text file and in the data preview it showed the correct data. but when i tell it to run the import i get an error saying:
"Not enough storage is available to complete this operation.
Not enough storage is available to complete this operation."
what can i do?
December 15, 2004 at 5:40 am
anyone? any ideas?
December 15, 2004 at 5:58 am
You've already checked available space on your drives?
What is the size of that file?
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
December 15, 2004 at 7:06 am
weell the drive that stores the SQL Server Data is 130 GB and there is currently 128 GB free.
if i go into enterprise manager and look at the properties for the database, here's what i see:
General Tab:
Size: 1546.31 MB
Space Available: 80.32MB
Data Files:
Space Allocated(MB):105
Automatically grow file: checked
By percent: 10
Unrestricted fiel Growth
any ideas what i need to do to make this import work?
December 15, 2004 at 7:06 am
December 15, 2004 at 7:31 am
maximum file size is set to "unrestricted growth"
December 15, 2004 at 7:38 am
You didn't mention how large that file is that you want to import.
--
Frank Kalis
Microsoft SQL Server MVP
Webmaster: http://www.insidesql.org/blogs
My blog: http://www.insidesql.org/blogs/frankkalis/[/url]
December 15, 2004 at 7:39 am
the text file (.dat) that i am tryign to import is approx 300K
December 15, 2004 at 8:24 am
The majority of the articles that returned when I 'googled' the error message have to do with known bugs with ADO. Some of these articles delt with SQL Server CE, other articles mentioned a range of conditions for getting the error message. The first thing I would do is verify that you have the latest releases of SQL Server, MDAC, etc. That was the prevailing resolution.
December 15, 2004 at 8:30 am
well i think i actually got it but in a very roundabout way -
when i was importing the data i was having SQL server create the table for me. the reason i was doing this is because the text file has a little over 200 columns and i didnt want to create them by hand. so what i did was to import the data to excel and then import the excel file to SQL server. it gave me an error about a data type conversion but it did create the table so theni tweaked the column data types and retried the actual import a few times till i got it right.
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply