suggestion for improvement in next release.

There’s one thing that bugs me to no end in ToadSS. We use a template for our stored procedures that contains try…catch and transaction handling code predefined. It’s set to read only on the file system so people don’t accidentally save with their code. In MS, I can open the file, modify it and save and MS will prompt me to save with a new name or override. In ToadSS I can’t make a change to the file until I go to the file system and change the attribute to read/write. If I do it in Toad or change it while the file is open Toad doesn’t recognize the change. So I have to 1) close the file, 2) go to file system and copy the file to a new name (the name of the sproc I’m creating) 3) change the new file to rw, 4) open the file in Toad. That’s WAY inconvenient to me.

Why do we save our SP’s to a file? Because I require the developers to script every change they make to the database so we can build a rollout for QA and then Production.


Hi Tim,

Just wonder have you tried the schema compare functionality in Toad? It is designed to compare and generate synch script for rollouts between dev and QA/production servers.


I love this idea. My shop also requires files for our sprocs.

Yes, Valentin, I am familiar with schema compare and use it occasionally. But just because a schema is different doesn’t mean the changes should be migrated in_this_release. Also, I require that the developers know the changes they are making and have them reviewed by a DBA before they go into production. Also, part of the purpose for a QA rollout is to ensure that the rollout process is complete, something a schema compare can’t do. Thus, it is required that; one, every database change be scripted and two, every script use the template so we get appropriate error checking handled and standards enforced.


This feature is already in 5.0 – you can test with the latest beta.

In 5.0 you can edit a read-only file opened in the editor, but when you go to
save it will prompt for a new filename with a save as dialog. If you wish to
then overwrite the original file, you would have to go to the operating system
to flip the read-only attribute. Another option is to right-click the tab for
the file in Toad and click the “File Properties” action to change it
right from Toad.


As David menioned, this is being addressed in 5.0. But as I understand it, the change will only prompt you for a new file name and not allow an overwrite.

I see what SSMS does, but I think it’s actually rather dangerous behavior to allow an overwrite of a read-only file so easily. SSMS also appears to leave the file with the read-only flag disabled; meaning you need to revisit the file to turn it back on.

Office 2007 prevents saves to a read-only file.

What you can do in Toad 5.0 if you need to save the file with the same name is to open up the properties for the file in the File | Save dialog (rather than having to go to Explorer) and turn off the Read Only flag. Once you save, you’ll be in the same position with SSMS and you’ll need to reset the Read only flag - which you can also do easily by opening File | Save As.


Thank you for the response David, I agree with you on the overwrite. I just want
to save with a new name and have it set the attribute right. So the
functionality in v5.0 is perfect for me. Thanks,