I’ve been tossing around some ideas for my blog. One of which is to provide a quick tech tip… or a SQL Tidbit. The idea is to keep me writing until I get used to blogging EVERY week. Hopefully in a few months I’ll have more SQL Tidbits than there are Grape Leaves in this picture.
So let’s get started with the first SQL Tidbit.
In the beginning…
I’ve been using ER/Studio Data Architect for a few years now. If you’re not familiar with it, it’s used for modeling and maintaining database schemas. I love this product, but I’m not a big fan of the default application (Universal ISQL) that the change script is sent to. Mostly because Ctrl+A doesn’t work in the query window and I find it clunky.
At my previous company, one of my coworkers created an application that ran in the background. When it detected that a change script was ready to be deployed, it would capture it and open it in SSMS.
But there is an easier way
When I started at my current job, I was setting all the defaults that I like in ER/Studio Data Architect and I stumbled upon this setting that I didn’t know existed. This setting lets YOU pick the editor for the change scripts to be deployed to. I changed the path to SSMS and I didn’t have to see the default application any more. (WIN!)
To get to the setting, do the following.
1. Click on the Tools/Options menu item.
2. Click on the Tools tab on the right hand side of the dialog box.
3. Change the ISQL Path setting.
And that’s a wrap
In the next SQL Tidbit I’ll share a script for cleaning up temporary SQL objects.
[…] is on my favorite tool list. I’m sure you can guess what it is based on my last couple of posts here and here. It’s Embarcadero’s ER/Studio Data […]
[…] SQL Tidbits: No.1– Outputting from ER/Studio Data Architect Directly to SQL Server Management Stud… […]