• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 392
  • Last Modified:

SQL execution error when trying to open table with many cols

When trying to open a table (that someone else created) with a large number of cols SQLServer 2005 I get the following error:
Error Source: Microsoft.VisualStudio.DataTools
Exception has been thrown by the target of an invocation
I read somewhere the row length is 8060 - I guess this is the cause... Is there a workaround?


0
acdagirl
Asked:
acdagirl
  • 3
  • 3
1 Solution
 
YveauCommented:
Try running the code in Code Snippet.
I doubt there is some SQL error here. You might need to look for help in the zones for Visual Studio or the programming language you are using ...

If you can give us the table def, we can calculate the column length (as you can do yourself of course) but when you try to create a table with a record def that is too long, you will get an error and you won't be able to create the table. So I have strong indication that the programming language or tool you are using is having some problems with the number of column. Not SQL Server ...

Hope this helps ...

select  count(*)
from    <Table>
-- should return only the number of records in the table.
 
select  *
from    <Table>
where   1 = 2
-- should return only the column names.
 
select  <column>
from    <Table>
-- select only one single column, not the whole (unknown) number of columns.
 
--

Open in new window

0
 
acdagirlAuthor Commented:
i'm opening the table in enterprise manager - there is not other tool here.
0
 
YveauCommented:
what about the select statements ?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
acdagirlAuthor Commented:
if I do a range it's ok, if I try to select all it fails with the same error.
0
 
YveauCommented:
Yep ... the SSMS is also just an application. The datagrid controls which are used for the SSMS also have there boundaries ... just have to live with it. You might want to make a case with MS for this ...
I've noticed these issues as well with several sort of operations on larger tables ...

But in the end ... scripting is always better ... and has never failed me :-)

Hope this helps ...
0
 
acdagirlAuthor Commented:
ok thanks
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now