Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Patent Agent
Starting Member
4 Posts |
 Posted - 2011-05-27 : 07:21:07
|
Oh boy. I have this lovely error: 'Error HRESULT E_FAIL has been returned from a call to a COM component. (mscorlib)' When trying to use SQL Server Management Studio 2008 R2. Upon trying to open a .sql file, the error comes.I read a bit that this might relate to Regions/Languages settings. I am strangly on a French maching at the moment - I usually develop on a California machine. But the French machine is total set up as if it were in the US as far as I know. I chose US English in the control panel.The advanced information for the error looks like this:  |
|
|
Patent Agent
Starting Member
4 Posts |
Posted - 2011-05-27 : 08:21:52
|
| Update: This might not relate to Region at all. I've now been able to write a sql file from VS 2008 - that file opens fine in Management Studio 2008 R2 and runs fine. The only difference being - I left out one table which is full of binary image data. Leaving out that one table seems to do the trick. But what is it in that table (which has worked fine in the past) that is making the problem? The table is identical to prior working versions - except for the new data which has recently been put in there. Can binary image data queer a file to cause this error? How will I find which record is the problem record? Ouch. This sucks. |
 |
|
|
Patent Agent
Starting Member
4 Posts |
Posted - 2011-05-27 : 08:39:37
|
| Because this file in pretty heavy in size - a few hundred small images - could it be making trouble because of its size? If so, how do I break it into parts to transfer? Any help? |
|
|
|
elaine
Starting Member
6 Posts |
Posted - 2012-01-22 : 11:55:58
|
| Hi, have you solved the problem finally?I have this problem now, the same as yours. The file is also very heavy in size, like 45GB.When try to open a .sql file with smaller size(1000KB), it works very well.How to solve this error? I am left very limited time to resolve it by the manager. Does anyone can help me? |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2012-01-22 : 11:59:46
|
| I would be very surprised if you can open a 45GB SQL file in SSMS. Its not impossible ... but I reckon it is highly improbably. |
|
|
|
elaine
Starting Member
6 Posts |
Posted - 2012-01-22 : 12:05:32
|
| Then how can I deal with the problem? Since the data is really huge. we have 5000 files in total....Can I only import them one by one?It needs a long long time..... |
|
|
|
elaine
Starting Member
6 Posts |
Posted - 2012-01-22 : 12:06:42
|
| And the manager is pushing high pressure on me to finish before tomorrow morning.Is there anything I can do except importing the 5000 files one by one? |
|
|
|
GilaMonster
Master Smack Fu Yak Hacker
4507 Posts |
Posted - 2012-01-22 : 12:21:01
|
| Why are you using .sql files to import huge amounts of data? Surely something like BCP or bulk insert with an appropriately delimited source file would be way easier (first to produce, second to insert)--Gail ShawSQL Server MVP |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2012-01-22 : 13:51:28
|
| If there are 5,000 files then run them individually with OSQL or similar. |
|
|
|
|
|
|
ManStud 2008 R2 file open error