Toad World® Forums

Invalid SQL generated with script options drop and check exists


#1

Hi Michael,

When checking the existence before the drop remove the use acces and the go statements between begin and end.

Create procedure should be the first statement in a query batch therefore the existence can’t be checked.

I also have a problem with the square brackets, if the name of the procedure is 29 or 30 characters long, which is the maximum allowed in my configuration, the server (ASE 12.5.3) tells me that the name is too long. With ASE 15.5 there is no problem.

Why is there a [dbo]. on the drop procedure statement. I am not using fully qualified object names.

ScreenShot247.jpeg


#2

Hello Jean-Pierre,

I created and fixed CR 81,926 for the invalid SQL. I also created CR 81,957 to investigate the issue with the square brackets.

Thanks.


#3

Hello Jean-Pierre,

In the next beta the square brackets will only appear when using non-standard object names.

Thanks.