rb11291978
Programmer
How compatible is SQLDMO to VBNet?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
SQLDMO & SQLNS vs VBNet
- Thread starter rb11291978
- Start date
- Status
NoCoolHandle
Programmer
SQLDMO is nothing more than a "COM object" written to expose SQL servers "Management Objects" to a com compliant client..
.Net can be com compliant via com interop (something that happens when you reference a com object at the project level automaticly)
What you will find however is that unlike the good old VB6 client that you need to dim your variables as the "interface" version of the class you need. If you don't, it tells you it doesn't know what you are talking about.
Bottom line, it will work, but not as clean as the good old client. Good news is that with sql2005 you now have a native dotnet management interface (can't remember what it is called off the top of my head) and has done away with dmo.
However, you can do anything in .net that you could do in Visual Studio 6. It might just take a little time.
For non managemnt functionality (and even for a lot of management type things) you can use a sqlclient.sqlconnection and sqlclient.sqlcommand and stored proceedures to perform exactly the same functionality without any problems. (about the only function I haven't been able to do with standard tsql is list all sqlservers on the network)
For what it is worth (hopefully everything here is correct - it has been a while since i tried dmo and .net but i think you can probably accept what I have said as gospel - interfaces start with an i and have a funky icon that looks like a figure 8 from rock climbing)
Rob
.Net can be com compliant via com interop (something that happens when you reference a com object at the project level automaticly)
What you will find however is that unlike the good old VB6 client that you need to dim your variables as the "interface" version of the class you need. If you don't, it tells you it doesn't know what you are talking about.
Bottom line, it will work, but not as clean as the good old client. Good news is that with sql2005 you now have a native dotnet management interface (can't remember what it is called off the top of my head) and has done away with dmo.
However, you can do anything in .net that you could do in Visual Studio 6. It might just take a little time.
For non managemnt functionality (and even for a lot of management type things) you can use a sqlclient.sqlconnection and sqlclient.sqlcommand and stored proceedures to perform exactly the same functionality without any problems. (about the only function I haven't been able to do with standard tsql is list all sqlservers on the network)
For what it is worth (hopefully everything here is correct - it has been a while since i tried dmo and .net but i think you can probably accept what I have said as gospel - interfaces start with an i and have a funky icon that looks like a figure 8 from rock climbing)
Rob
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question