[dba-VB] SMO was Projects vs Solutions

Hi John --

Yes, I understand that.
I'm wondering what for do you learning this stuff? - Just out of curiosity
or do you plan to implement some custom applications using
Microsoft.SQLServer.* ?

Thank you.

--
Shamil

-----Original Message-----
From: dba-vb-bounces at databaseadvisors.com
[mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby
Sent: Saturday, November 21, 2009 5:06 AM
To: Discussion concerning Visual Basic and related programming issues.
Subject: Re: [dba-VB] SMO was Projects vs Solutions

That is used for manipulating the SMO object and SQL Server.

I am just learning this stuff and do what the demos tell me to do.

John W. Colby
www.ColbyConsulting.com


Shamil Salakhetdinov wrote:
> Hi John,
> 
> By Microsoft.SQLServer.* I mean all the namespaces you mentioned
> 
>> Microsoft.SQLServer.SMO
>> Microsoft.SQLServer.SMOEnum
>> Microsoft.SQLServer.SQLEnum
>> Microsoft.SQLServer.ConnectionInfo
> 
> As well as their classes and those classes enumerations, methods,
> properties, events etc.
> 
> <<<
> I do have multiple servers running SQL Server.  
> The default is Azul but I may need to reference 
> Stonehenge.
> But do you need to change the reference(/connection string information) to
> SQL Server after you have your program started?
> Do you need to enumerate SQL Server objects to solve your customers'
tasks?
> Or maybe you have developed a kind of code generator, which does need to
> enumerate MS SQL Server objects and some of their properties to generate
> some custom code? - I can understand the latter - if you have to develop a
> lot of repetitive custom code then it's often useful to generate it...
> 
> Thank you.
> 
> --
> Shamil
> 
> 

 

__________ Information from ESET NOD32 Antivirus, version of virus signature
database 4626 (20091120) __________

The message was checked by ESET NOD32 Antivirus.

http://www.esetnod32.ru