Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
jbates99
Constraint Violating Yak Guru
396 Posts |
Posted - 2013-08-27 : 14:03:05
|
Sometimes it can be difficult to identify all of your SQL Server installations.Is command osql /L still the best technique?Thanks Jack |
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2013-08-29 : 05:58:43
|
Try SQLCMD /L , if using sql server versions from 2005. Jack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
djj55
Constraint Violating Yak Guru
352 Posts |
Posted - 2013-08-29 : 08:58:58
|
If you are interested in a third party solution, i.e. cost. I use Idera SQL Administrator Tool which has a SQL instance search tool.I do believe there is a free trial.djj |
|
|
jackv
Master Smack Fu Yak Hacker
2179 Posts |
Posted - 2013-09-01 : 06:10:54
|
Once you've captured the sql server instances , store in a spreadsheet or other repository. Run daily health checks \ etc . Maintaining an inventory management is important in DR situationsJack Vamvas--------------------http://www.sqlserver-dba.com |
|
|
jbates99
Constraint Violating Yak Guru
396 Posts |
Posted - 2013-09-03 : 10:03:10
|
Thanks jacky and djj55.I ran SQLCMD /L and it returned the same list of instances - except 1. OSQL /L picked up a second instance on a server that has Sharepoint installed.SQLCMD /L did not listg that sharepoint (named instance)It just seems to be difficult to know for certain you have found all sql server instances.If anyone has a solid technique, pls let me know.Thanks |
|
|
|
|
|