| Author |
 Topic  |
|
|
AskSQLTeam
Ask SQLTeam Question
USA
0 Posts |
|
|
AjarnMark
SQL Slashing Gunting Master
USA
3246 Posts |
 Posted - 08/16/2001 : 13:17:55
|
Great info JD! I like the looks of the SQLPing utility. And we certainly can use some people around here becoming more security-conscious, so that link to http://www.sqlsecurity.com will be handy.
Thanks!
------------------------------------------------------------------
Contractor$ never die, they just leave for higher-paying project$. |
 |
|
|
lupester
Starting Member
USA
1 Posts |
Posted - 09/10/2001 : 14:58:24
|
Is there a way to run these commands on different domains than the current one your computer belongs to?
Regards,
Eric
quote:
Jerald writes "Dear SQL Team, I am working on SQL Server 7 and also on SQL 2000. Now our company has many SQL Servers running on the Network and also in different domains. Now is there a way where I can find out which SQL Servers are currently running on the Network and list them in the Front end (using VB, to display the list of servers avalible in a combo)"<P>Article <a href="/item.asp?ItemID=5403">Link</a>.
|
|
|
|
vrbhatt
Starting Member
3 Posts |
Posted - 10/10/2003 : 10:55:37
|
I need to List all the SQL Servers on the network programatically in .NET.
I am able to so it using .listSQL.....
But I need to install the application at clients place and "oSQLApp.ListAvailableSQLServers()" requires SQL Server 2000 Service Pack 2/3 which can be done only if SQL Server is installed on the client's machine [which is not feasible I think].
Can U please help me out in this matter.
Thanks for your help.
|
|
|
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
Posted - 10/10/2003 : 12:57:19
|
I wouldn't think that doing this in an application would be a wise idea. Scanning the network for this can be very slow.
Installing SQL Server on the client's machine would require licenses for each client. I doubt that you want to go down that route.
I would recommend against doing this in your application.
You could always use the scan utility that MS has:
http://www.microsoft.com/downloads/details.aspx?familyid=9552d43b-04eb-4af9-9e24-6cde4d933600&displaylang=en
I have used this utility before so that we can find unlicensed servers and uninstall them. It was very, very slow though. It is not something that you want to bundle in an application. I'm not even sure that you would be allowed to do this anyway.
Tara |
|
|
|
vrbhatt
Starting Member
3 Posts |
Posted - 10/11/2003 : 06:18:27
|
Thanks for the link.
Did you mean SQL Scan (Sqlscan.exe) for the purpose.
I didn't understand the following :
Instances of SQL Server 2000 with Service Pack 2 (SP2) and security patch MS02-039, MS02-043, MS02-056, or MS02-061, or instances with SP3 or later, are not vulnerable. Computers running SQL Server 7.0 and earlier are not vulnerable.
Thanks for help. |
|
|
|
tkizer
Almighty SQL Goddess
USA
35007 Posts |
Posted - 10/13/2003 : 12:20:18
|
SQLScan is what you want. It is used to detect vulnerabilities (slammer worm) on the network, but it also identifies instances. The statement that you quoted is just saying that if the instances have SP2 with the security patches or SP3 or later, then they are not vulnerable to the slammer worm. You don't need to worry about this one, unless you are checking for vulnerabilities. You just care about finding the instances, which this utility will do as well. (at least that's what I remember when I ran it last time)
Tara |
|
|
|
vrbhatt
Starting Member
3 Posts |
Posted - 12/04/2003 : 04:21:11
|
| Thanks buddy. The scan exe worked. |
|
|
| |
Topic |
|
Article: Finding SQL Servers running on a network
