Sorry and thanks. Just using SMO, you need to know that to do anything.
On Fri, May 1, 2020 at 4:01 AM Alan Bourke wrote:
> On Thu, 30 Apr 2020, at 5:11 PM, Stephen Russell wrote:
> > What do you want to do through SMO?
>
> It's actually Paul Newton who has the requirement, which is to discover
On Thu, 30 Apr 2020, at 5:11 PM, Stephen Russell wrote:
> What do you want to do through SMO?
It's actually Paul Newton who has the requirement, which is to discover SQL
Server instances on the network.
--
Alan Bourke
alanpbourke (at) fastmail (dot) fm
_
Hi Stephen
Get a list of SQL Servers on the network - but see my latest post
Paul
-Original Message-
From: ProfoxTech On Behalf Of Stephen Russell
Sent: 30 April 2020 17:11
To: profoxt...@leafe.com
Subject: Re: SQL Server Shared Management Objects (SMO)
Sent by an external sender
What do you want to do through SMO?
On Thu, Apr 30, 2020 at 10:38 AM Alan Bourke
wrote:
> On Thu, 30 Apr 2020, at 4:16 PM, Stephen Russell wrote:
> > What SMO does for you is also available via powershell. Because I have
> the
> > app written I don't work much in powershell for SQL Server analy
I don't know that this is fully in-line with the subject of this thread,
but, just I want share this in case it helps anyone:
A few years ago I made a blog post about using PowerShell to execute
commands against Sql Server.
http://mattslay.com/sql-server-queries-using-powershell-lesson-1/
On Thu, 30 Apr 2020, at 4:16 PM, Stephen Russell wrote:
> What SMO does for you is also available via powershell. Because I have the
> app written I don't work much in powershell for SQL Server analysis.
Steven
Yes indeed although leveraging Powershell as part of an EXE distributed to end
users
What SMO does for you is also available via powershell. Because I have the
app written I don't work much in powershell for SQL Server analysis.
On Thu, Apr 30, 2020 at 2:58 AM Alan Bourke wrote:
>
> Paul
>
> There is no COM interface to SQL-SMO, so you would have to create a .NET
> assembly wit
Version"]);
Console.WriteLine(" " + dr["IsLocal"]);
}
Console.WriteLine("Finished ...");
Console.ReadKey();
}
}
}
-Original Message-
From: ProfoxTech On Behalf Of Alan Bourke
Sent: 30 April 2020 08:57
T
Alan
Thanks for the reply - I suspected that's what I might have to do.
Paul
-Original Message-
From: ProfoxTech On Behalf Of Alan Bourke
Sent: 30 April 2020 08:57
To: profoxt...@leafe.com
Subject: Re: SQL Server Shared Management Objects (SMO)
Sent by an external s
Paul
There is no COM interface to SQL-SMO, so you would have to create a .NET
assembly with a COM-callable wrapper exposing the functions you want I think.
Or even just a .NET EXE which dumps any results to a text file that the vfp
SIDE CAN READ.
--
Alan Bourke
alanpbourke (at) fastmai
I have a huge application built in sometime 2009-10 for managing SQL Server
stored procedures as well as submitting standard daily statements to the
variety of servers and instances I manage.
I don't know if you are going to be able to create all of the container
objects that are necessary to work
Thanks Tracy - my mistake we are in fact currently using loDMO =
CreateObject("sqlDMO.Application")
Paul
-Original Message-
From: ProfoxTech On Behalf Of Tracy Pearson
Sent: 29 April 2020 16:59
To: profoxt...@leafe.com
Subject: RE: SQL Server Shared Management Objects (SMO
The COM object you are creating is named "sqlSMO", are you sure this isn't
already the object you are looking for?
Tracy
-Original Message-
From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Paul
Newton
Sent: Wednesday, April 29, 2020 11:56 AM
To: profoxt...@leafe.com
Sub
13 matches
Mail list logo
