|
|
|
|
|
One of the biggest hurdles in managing a
large environment or one that you weren't involved in all of the design decisions is in
finding things. Which server and database contains that customer table? Which
database contains that really neat stored procedure that you spent 2 weeks creating
sometime last year? I'm sure everyone out there has run a search on their local hard drives or across the network for a particular file. It's hunt and guess to find it and sometimes takes several searches. Wouldn't it be nice to be able to easily run those same types of searches against your SQL Servers? Many people don't have some of the management tools available that include some of this functionality. SQL Server Find is a little known utility that can give you this functionality. Like all good utilities, it does exactly one thing and does it well. The first step when starting up SQL Server Find is to register your servers. It has the capability to handle trusted or standard connections. It is developed for MS SQL Server 6.5 and 7.0 and can handle both trusted and standard connections. After registering your servers, you are now ready to find what you are looking for. I'm sure the figure below looks VERY familiar to anyone on a Windows platform. I'm sure I don't have to explain this to anyone since you've all searched for files before.
The big advantage that SQL Server Find gives you is the ability to search multiple servers and databases in a single search. You simply check off the databases you want to search.
|
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.
