|
|
|
|
|
DBArtisan 5.03 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 Clicking the options button will gain you access to customize the look, feel, and functioning of DBArtisan. The General tab is the first place where you might want to make changes. When you highlight an object and hit enter or double click on an object, an editor will open. The General tab controls how many editors can be opened in a single operation. When I am doing a significant amount of editing, I will normally have this value set to between 20 and 50. You have to be careful with the resources available on your machine. The max entries in output window is something else you will want to change. I always set this to 5000 which is the maximum. 1500 lines in the output window may seem like a lot, but after you have transferred a single database with a couple hundred objects, you will quickly see that 1500 is pretty low. Even 5000 is a rather low number and I constantly blow over that limit as well. I would like to see another option on this screen for a file name. Output all messages to the file I specify and only show the last x number in the output window. Then I am assured of being able to access all of the history that I need. I also deselect the confirm on exit. By leaving this on, every time you go to exit DBArtisan, you will be prompted if this is what you really want to do. I can count on one hand the number of times I have said no since I started using DBArtisan.
I mentioned a configuration setting back when I was discussing the Script Execution Facility. This tab contains that setting. When I first started using the Script Execution Facility I ran head first into a brick wall. I had a script that I needed to execute against 57 servers. I popped open the Script Execution Facility, put in the script, checked off all 57 server and hit execute. The script ran along just fine when everything crashed and burned on the 23 server. Turns out that I already had 2 open connection + the 23 that were opened with the Script Execution Facility nailed the hard coded maximum of 25 open datasources. It was admitted that 25 was hardcoded into the app and that the only reason was amount of resources consumed. I was running on a machine with 384MB of RAM, so the last thing I was concerned with were resources. After some discussions about this, the Max DB Processes setting was added as a configuration option. I normally set this to 100 except when I am making some very major changes and then I will increase it. I have had this setting as high as 550 with 530 datasources open at one time. If you are running an environment with more than 25 servers (the default setting), you will want to increase this value.
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.
