|
|
|
|
|
DBArtisan 5.03 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 The Explorer options are something you may want to change. The default setting are shown below and this is how I have them set. You may want to see the system objects instead of having them filtered out of the display. If you have a large number of objects owned by several different logins, you may choose to view by object owner instead of viewing by type. The organization of the Explorer can also be dynamically selected using the bars at the top/bottom of the left hand pane.
For the ISQL window, I would suggest leaving just about all of the defaults alone. I would highly suggest turning off the auto-save. This is not because it isn't a very useful feature, but because it is not implemented correctly. The auto-save feature in something like Word will take a copy of a document and save it on a regular basis into a separate "crash" file. If Word terminates abnormally, it will load this "crash" file automatically when it is restarted. DBArtisan does not generate a "crash" file during auto-save. Instead, it saves over the top of the existing file. I found this one very quickly when it managed to blow away about 30 minutes worth of work when I wanted to close without saving and revert to the original. The only problem is that the original had been overwritten. The other option I would change is the save most recent x commands. I set this to the maximum to provide the most undo capability possible.
DBArtisan 5.03 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
All content on this site, except where noted, represents an original work of Michael R. Hotek and is protected by applicable copyright laws. The SQL Server FAQ is the sole work of Neil Pike. No page, portion of a page, or download may be used for commercial purposes in whole or in part without the express, written permission of the applicable author.
