Help gathering SQL info from all servers - noobie alert :)

I'm a domain admin, not a SQL guy. Unfortunately I have been tasked with
finding all SQL servers in the company and coming up with a migration plan
to a single SQL cluster.
The issue at hand is that I'm hoping not to try to reinvent the wheel... is
there any script (vb, js, osql, something), that will query a list of known
SQL servers and output the database names and sizes to a text/csv file?
If it could go one step further and give me other info like usernames and
such that would be great too!
Thanks for any help you can give!
Aaron
Do a scan for anything listening on port 1433 and you should find all of
your SQL Servers. You will have to factor out anything that is nothing more
than local MSDE due to some application install.
Once you have the server names, you can connect to them with a trusted
connection (proxies your domain admin authority). The list of databases can
be found by using "select * from master.dbo.sysdatabases". The list of
users can be found by using "select * from master.dbo.sysxlogins".
Mike
Mentor
Solid Quality Learning
http://www.solidqualitylearning.com
"livin" <livin@.@.cox.net> wrote in message
news:rDxuf.676$B93.22@.fed1read07...
> I'm a domain admin, not a SQL guy. Unfortunately I have been tasked with
> finding all SQL servers in the company and coming up with a migration plan
> to a single SQL cluster.
> The issue at hand is that I'm hoping not to try to reinvent the wheel...
> is there any script (vb, js, osql, something), that will query a list of
> known SQL servers and output the database names and sizes to a text/csv
> file?
> If it could go one step further and give me other info like usernames and
> such that would be great too!
> Thanks for any help you can give!
> Aaron
>
>
|||Hi
Look at SQLRecon on http://www.sqlsecurity.com/DesktopDe...aspx?tabid=26,
you will need the rights to access these servers to audit the database
details you may want to look at
http://www.sqlservercentral.com/scri...?scriptid=1589
John
"livin" <livin@.@.cox.net> wrote in message
news:rDxuf.676$B93.22@.fed1read07...
> I'm a domain admin, not a SQL guy. Unfortunately I have been tasked with
> finding all SQL servers in the company and coming up with a migration plan
> to a single SQL cluster.
> The issue at hand is that I'm hoping not to try to reinvent the wheel...
> is there any script (vb, js, osql, something), that will query a list of
> known SQL servers and output the database names and sizes to a text/csv
> file?
> If it could go one step further and give me other info like usernames and
> such that would be great too!
> Thanks for any help you can give!
> Aaron
>
>
|||Hi living,
just for fun I wrote a Application for you to gather this information
for all servers / all databases which put this information into an XML
file which can be easily used in Excel or some other program. If you
(or any other guy) is Interested in just drop me a mail, i=B4ll send it
to you, later on after finishing the building of my new portal
www.sqlserver2005.de I will put it up there. It uses the new SQL.SMO
and the .net 2.0 to collect this information.
HTH, Jens Suessmeyer.
|||You guys rock!
Thanks for helping out a noobie... I DL'd all the stuff and will have fun
with it this week!
Jens... sending you an email now.
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1136325248.839414.309600@.g49g2000cwa.googlegr oups.com...
Hi living,
just for fun I wrote a Application for you to gather this information
for all servers / all databases which put this information into an XML
file which can be easily used in Excel or some other program. If you
(or any other guy) is Interested in just drop me a mail, ill send it
to you, later on after finishing the building of my new portal
www.sqlserver2005.de I will put it up there. It uses the new SQL.SMO
and the .net 2.0 to collect this information.
HTH, Jens Suessmeyer.

HELP - need to kill big transaction that's taking too long to rollback

Hi all,
I have a big transaction running on a table that I had to kill and
rollback. Unfortunately, the transaction has been rolling back for 1.5
hours and is supposedly only 6% done rolling back. I need to stop this
transaction, and I'm looking for the fastest way to do it with doing
the least amount of damage.
Is there any nuke button that I can press to kill this process with
extreme prejudice? - at this point I don't care about the integrity of
the table I was running the transaction on - I just want it to die.
Is there any way to force the table to drop, thus killing the process?
Is there any way to make a new log file for this database, and kill the
log file that has the rolling back?
If I stop SQL Server, will it try to wait until the transaction is
done/rolledback before it will actually stop?
Please HELP! Thanks in advance
-Rob
Stop the server service?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"robh1999atgmail" <RobH1999@.gmail.com> wrote in message
news:1159460802.483348.29370@.d34g2000cwd.googlegro ups.com...
> Hi all,
> I have a big transaction running on a table that I had to kill and
> rollback. Unfortunately, the transaction has been rolling back for 1.5
> hours and is supposedly only 6% done rolling back. I need to stop this
> transaction, and I'm looking for the fastest way to do it with doing
> the least amount of damage.
> Is there any nuke button that I can press to kill this process with
> extreme prejudice? - at this point I don't care about the integrity of
> the table I was running the transaction on - I just want it to die.
> Is there any way to force the table to drop, thus killing the process?
>
> Is there any way to make a new log file for this database, and kill the
> log file that has the rolling back?
> If I stop SQL Server, will it try to wait until the transaction is
> done/rolledback before it will actually stop?
> Please HELP! Thanks in advance
> -Rob
>

HELP - need to kill big transaction that's taking too long to rollback

Hi all,
I have a big transaction running on a table that I had to kill and
rollback. Unfortunately, the transaction has been rolling back for 1.5
hours and is supposedly only 6% done rolling back. I need to stop this
transaction, and I'm looking for the fastest way to do it with doing
the least amount of damage.
Is there any nuke button that I can press to kill this process with
extreme prejudice? - at this point I don't care about the integrity of
the table I was running the transaction on - I just want it to die.
Is there any way to force the table to drop, thus killing the process?
Is there any way to make a new log file for this database, and kill the
log file that has the rolling back?
If I stop SQL Server, will it try to wait until the transaction is
done/rolledback before it will actually stop?
Please HELP! Thanks in advance
-RobStop the server service?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"robh1999atgmail" <RobH1999@.gmail.com> wrote in message
news:1159460802.483348.29370@.d34g2000cwd.googlegroups.com...
> Hi all,
> I have a big transaction running on a table that I had to kill and
> rollback. Unfortunately, the transaction has been rolling back for 1.5
> hours and is supposedly only 6% done rolling back. I need to stop this
> transaction, and I'm looking for the fastest way to do it with doing
> the least amount of damage.
> Is there any nuke button that I can press to kill this process with
> extreme prejudice? - at this point I don't care about the integrity of
> the table I was running the transaction on - I just want it to die.
> Is there any way to force the table to drop, thus killing the process?
>
> Is there any way to make a new log file for this database, and kill the
> log file that has the rolling back?
> If I stop SQL Server, will it try to wait until the transaction is
> done/rolledback before it will actually stop?
> Please HELP! Thanks in advance
> -Rob
>

HELP - need to kill big transaction that's taking too long to rollback

Hi all,
I have a big transaction running on a table that I had to kill and
rollback. Unfortunately, the transaction has been rolling back for 1.5
hours and is supposedly only 6% done rolling back. I need to stop this
transaction, and I'm looking for the fastest way to do it with doing
the least amount of damage.
Is there any nuke button that I can press to kill this process with
extreme prejudice? - at this point I don't care about the integrity of
the table I was running the transaction on - I just want it to die.
Is there any way to force the table to drop, thus killing the process?
Is there any way to make a new log file for this database, and kill the
log file that has the rolling back?
If I stop SQL Server, will it try to wait until the transaction is
done/rolledback before it will actually stop?
Please HELP! Thanks in advance
-RobStop the server service?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"robh1999atgmail" <RobH1999@.gmail.com> wrote in message
news:1159460802.483348.29370@.d34g2000cwd.googlegroups.com...
> Hi all,
> I have a big transaction running on a table that I had to kill and
> rollback. Unfortunately, the transaction has been rolling back for 1.5
> hours and is supposedly only 6% done rolling back. I need to stop this
> transaction, and I'm looking for the fastest way to do it with doing
> the least amount of damage.
> Is there any nuke button that I can press to kill this process with
> extreme prejudice? - at this point I don't care about the integrity of
> the table I was running the transaction on - I just want it to die.
> Is there any way to force the table to drop, thus killing the process?
>
> Is there any way to make a new log file for this database, and kill the
> log file that has the rolling back?
> If I stop SQL Server, will it try to wait until the transaction is
> done/rolledback before it will actually stop?
> Please HELP! Thanks in advance
> -Rob
>