Error in updated Toad

Error in updated Toad

I’ve just updated Toad from 5.6.0.568 to 5.7.0.605

I’m now getting a SQL Server database error when attempting to view tables:

5.6.0.568 connecting OK:
Image 1 attached

5.7.0.605 connecting but with error (cannot view tables):
Image 2 attached


image002.png

I’ve just updated Toad from 5.6.0.568 to 5.7.0.605

I’m now getting a SQL Server database error when attempting to view tables:

5.6.0.568 connecting OK:
Image 1 attached

5.7.0.605 connecting but with error (cannot view tables):
Image 2 attached


image001.png

Hi Rob,

can you please send an exception trace file of toad to us? Many thanks in advance!

Please could you explain how I do that?
Rob

Hi Rob,
You can generate Support Bundle, that contain your Toad settings well as interested log files. To do this go to main menu Help\Support Bundle. You will be prompted to send an email with SB archive. You can post it here as attachment or send it to Valentin’s or my corporate email address.

Feel free to ask any questions.

Alexander

Bundle attached.
ToadSupportBundleToad for SQL Server.zip (112 KB)

Hi Rob,
thank you for the bundle! It was very useful to see ConnectionTrace.log file in it, thanks for turning on Execution Trace. BTW, please note that with enabled Execution trace you can expect some slowdowns, so turn it on only to investigate anything.

Regarding your issue - we see what sql is leading to the exception but we have no idea why. Can you please copy SQL below to the Editor and try to execute it agains TMS and any other your DB. Please get back with your results.

SET NOCOUNT ON;

SELECT
COUNT(1)
FROM
sys.all_objects obj
INNER JOIN sys.schemas sch ON sch.schema_id = obj.schema_id
INNER JOIN sys.indexes idx
ON (idx.object_id = obj.object_id) AND
(idx.index_id
LEFT OUTER JOIN sys.data_spaces dsidx
ON dsidx.data_space_id = idx.data_space_id
LEFT OUTER JOIN sys.extended_properties eprop
ON obj.[object_id] = eprop.major_id AND
eprop.[name] COLLATE database_default = N’MS_Description’ AND
eprop.minor_id = 0
WHERE
(obj.type COLLATE database_default = N’U’)

Error:25/07/12 10:59:34 0:00:00.144: Lookup Error - SQL Server Database Error: Incorrect syntax near ‘]’.

14: SET NOCOUNT ON;

SELECT

COUNT(1)

FROM

sys.all_objects obj

INNER JOIN sys.schemas sch ON sch.schema_id = obj.schema_id

INNER JOIN sys.indexes idx

ON (idx.object_id = obj.object_id) AND

(idx.index_id < 2)

LEFT OUTER JOIN sys.data_spaces dsidx

ON dsidx.data_space_id = idx.data_space_id

LEFT OUTER JOIN sys.extended_properties eprop

ON obj.[object_id] =]

On all databases getting following when running the script:

Rob

oops, for some reason I posted not accurate SQL. It is forum issue.
See attached file for the correct sql.
2Rob.sql (613 Bytes)

Attached are screenshots of the results of the Sql run.
First run on the database producing the error (TMS), second on the ‘good’ database (ESCR).
Also attached are two support bundles produced after each script run.

Rob.
ToadSupportBundleToad for SQL Server_ESCR.zip (119 KB)

Attached are screenshots of the results of the Sql run.
First run on the database producing the error (TMS), second on the ‘good’ database (ESCR).
Also attached are two support bundles produced after each script run.

Rob.
sqlrun.docx (68.6 KB)

Attached are screenshots of the results of the Sql run.
First run on the database producing the error (TMS), second on the ‘good’ database (ESCR).
Also attached are two support bundles produced after each script run.

Rob.
ToadSupportBundleToad for SQL Server_TMS.zip (118 KB)

Rob, can you also advise compatibility levels for both dbs?