Discovering SQL databases

Hi, I'm in the process of migrating / decommissioning a series of SQL
servers.
Is there / are there any tools to sniff out any existing eroneous SQL
databases which people may have created by themselves?
TIAThere are several ways to accomplish the task. Here are a couple ideas.
User SQLPing. Read about its usage here:
http://www.sqlteam.com/item.asp?ItemID=5403
A simple bat file idea:
http://www.databasejournal.com/feat...cle.php/3397981
And of course, any decent network scanning tool.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Stu" <lbwer@.blah.com> wrote in message
news:uzQExf$rGHA.2464@.TK2MSFTNGP03.phx.gbl...
> Hi, I'm in the process of migrating / decommissioning a series of SQL
> servers.
> Is there / are there any tools to sniff out any existing eroneous SQL
> databases which people may have created by themselves?
> TIA
>|||I suspect you mean sniff out instances of SQL Server, not databases.
I use SQL Recon: http://www.specialopssecurity.com/labs/sqlrecon/
Great utility to find any instance running on the network.
"Stu" <lbwer@.blah.com> wrote in message
news:uzQExf$rGHA.2464@.TK2MSFTNGP03.phx.gbl...
> Hi, I'm in the process of migrating / decommissioning a series of SQL
> servers.
> Is there / are there any tools to sniff out any existing eroneous SQL
> databases which people may have created by themselves?
> TIA
>sql

Disaster Recovery and Bulk Loads

We are in the process of migrating our database to SQL Server 2005 Standard
and I have a question regarding disaster recovery and bulk loads. We
periodically do bulk loads of data from files (csv's, flat files, etc). Our
current database product requires that we maintain a copy of the source file
used for these bulk data loads as part of its database recovery process. Th
e
question is - Does SQL Server require that we keep a copy of the source file
used for bulk data loads in order to recover a database using the log files?Hi Darren
I believe that's depend on how you set your recovery mode setting on your
SQL Server database (Full, Bulk-Logged, or Simple). If you set it up with
Full recovery, all the transaction done to SQL server get logged. And as lon
g
as the SQL Server transaction log get backed up regularly, you should be abl
e
to restore the database to point in time pretty easily, and you don't need t
o
have the source files for the bulk load. However, the downside of this would
be the log files for your SQL Server database would grow rapidly, especially
when you are performing the bulk load.
The Bulk Logged recovery has some limitation. Where it might not logged all
the bulk load transaction.
For more info on the recovery mode, you can check your SQL Server Book On
Line. I personally think that it would not hurt if you store your source
files of the bulk transaction.
Lucas
"Darren" wrote:
> We are in the process of migrating our database to SQL Server 2005 Standar
d
> and I have a question regarding disaster recovery and bulk loads. We
> periodically do bulk loads of data from files (csv's, flat files, etc). O
ur
> current database product requires that we maintain a copy of the source fi
le
> used for these bulk data loads as part of its database recovery process.
The
> question is - Does SQL Server require that we keep a copy of the source fi
le
> used for bulk data loads in order to recover a database using the log files?[/colo
r]