Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.

SQL Error (208): Invalid object name 'sys.extended_properties' Invalid object name 'sys.columns'

Ben070's profile image Ben070 posted 4 months ago in General Permalink

Hi, Been using HeidiSQl here and there since a year now, and I really like it. But I just got a new contract with users that utilize MS SQL server 2000 (ver 8.00.2039) This database is running quite well for their uses, never crashed.

But I'm trying to access their tables by viewing the data in Heidi without any success. Connection to the database is a charm. But I'm still having no success to see the data when selecting tables and clicking on the Data menu. I'm using the latest Heidi ver 10.2.0.5599, had also tried to downgrade to earlier version. but this message appears each time a clic a table. SQL Error (208): Invalid object name 'sys.extended_properties' Invalid object name 'sys.columns' see attached image.

Any help would be appreciated. Thanks

1 attachment(s):
  • 2019-08-02-15-59-38
Ben070's profile image Ben070 posted 4 months ago Permalink

Hi again, no one knows why this error (SQL Error (208) occurs?

ansgar's profile image ansgar posted 4 months ago Permalink

What is the query right before that error comes up? I guess some sql for retrieving columns of a table?

Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.
Ben070's profile image Ben070 posted 4 months ago Permalink

Hmm!? No SQL query was used yet, I am just connecting to the MS SQL server database, then choosing a table and just clicking on the data button tool. Always done it like this for just viewing the data in the tables. But I may have been using this tool the wrong way all along during the past year.

Thanks for your help ansgar

Ben

ansgar's profile image ansgar posted 4 months ago Permalink

There is a query right before that error comes up. I meant an internal one, not something you wrote yourself.

Ben070's profile image Ben070 posted 4 months ago Permalink

Sorry my bad! here's a screen capture to show the first message after connecting to the database. Again, thanks for your help

1 attachment(s):
  • First-connection
Code modification/commit 9d732a0 from Ansgar Becker <anse@heidisql.com>, 4 months ago, revision 5670
Restore compatibility to SQL Server 2000, when opening a table. See https://www.heidisql.com/forum.php?t=34331
ansgar's profile image ansgar posted 4 months ago Permalink

Next build should fix that. Please update in a few minutes and report back.

Related:

Ben070's profile image Ben070 posted 4 months ago Permalink

Sorry for the long delay, I did not had the chance to try the new version, thanks by the way! I'm now having a security issue at startup, I've installed the recommended MS OLE twice and rebooted, but this message is still occurring.(2019-08-12 12-52-09.png) But I'm still able to continue forward with Heidi, afterward most of the tables are giving me an error message upon clicking on data from most of the tables. I've included the bugreport.txt showing this Thanks. Ben

2 attachment(s):
Code modification/commit f4d2488 from Ansgar Becker <anse@heidisql.com>, 4 months ago, revision 5674
Try to fix missing schema in row counting query. See https://www.heidisql.com/forum.php?t=34331#p34439 and https://www.heidisql.com/uploads/34439-2-bugreport.txt
Ads were blocked - no problem. But keep in mind that developing HeidiSQL, user support and hosting takes time and money. You may want to send a donation instead.
ansgar's profile image ansgar posted 4 months ago Permalink

You should have a look at the new "Library" dropdown, if there is that new provider, and select that.

The error you get is related to a missing schema or database in an internal SELECT COUNT(), which I just attempted to fix in commit:f4d2488998ba585c971e672545b8a2843378572b

ansgar's profile image ansgar posted 4 months ago Permalink

Previous change, which fixed the first error was commit:9d732a003703877bfb37d583aafe38f0c0f4db7d

Ben070's profile image Ben070 posted 4 months ago Permalink

Thanks ansgar, so far so good I'm able to see the data per table, thank you.

Please login to leave a reply, or register at first.