Can We Manage SQL Server 2000 With WMI and Visual Basic.NET? - Summary
(Page 5 of 5 )
For those who are familiar with VBScript (especially working with WSH), you can still manage SQL Server 2000 using WMI, even without .NET Framework, using the following code:
sComputer = "server"
sSQLServer = "(local)"
Set oInstance = GetObject("winmgmts:{impersonationLevel=impersonate}//" & _
sComputer & "/" & "root/MicrosoftSQLServer:MSSQL_SQLServer.Name=" & _
Chr(34) & sSQLServer & Chr(34))
Set oOutParam = oInstance.Start()
If oOutParam.ReturnValue = 0 Then
WScript.Echo sSQLServer & " SQL Server started successfully"
Else
WScript.Echo "Starting of " & sSQLServer & " SQL Server failed with error " & _
oOutParam.Description
End If
The above is only a sample (especially for system administrators). You need to work with the “WScript” or “CScript” command at the MSDOS prompt to execute the above code. You can modify it according to your requirements.
I hope you can now confirm that we can use WMI to manage SQL Server 2000 together with the .NET framework. But one should consider that WMI is still an evolving technology. Day by day, WMI is getting updated with various features, opening a new world of “automated management” for system administration.
Since this is an introductory article, I could not go deep into “managing SQL Server 2000”. But you can expect a few more articles on this subject soon. Check this site regularly or sign up for the newsletter.
You can further enhance the coding I provided with all the necessary ingredients to polish it as an application. You can also shift this code to ASP.NET, which gives you the way to manage SQL Server 2000 using web applications together with WMI! Further areas of improvement include proper error or exception handling, using a few more flexible classes existing in WMI SQL Server Administration Provider, and so forth. You can get the entire list of classes (together with hierarchy) at MSDN online. Good luck.
Any comments, suggestions, bugs, errors, feedback, discussions etc. are highly appreciated at jag_chat@yahoo.com.
| DISCLAIMER: The content provided in this article is not warranted or guaranteed by Developer Shed, Inc. The content provided is intended for entertainment and/or educational purposes in order to introduce to the reader key ideas, concepts, and/or product reviews. As such it is incumbent upon the reader to employ real-world tactics for security and implementation of best practices. We are not liable for any negative consequences that may result from implementing any information covered in our articles or tutorials. If this is a hardware review, it is not recommended to open and/or modify your hardware. |
