Monday, March 19, 2012
Deploying SMO/RMO Applications to non-sql2005 servers.
Is it possible to deploy smo/rmo applications to servers and clients without installing the sql server 2005 client tools? Can I simply include the used assenblies or is there any dependance on some ActiveX objects or other configuration actions that must be performed for SMO/RMO to work?
regards,
Tore Birkeland
Yes, it is possible to deploy SMO/RMO applications without installing SQL Server 2005 client tools. The SQL Server 2005 RTM will include SMO redist setup file that you can use for your SMO-based applications. SMO relies on .NET Framework 2.0 and SQL Native Client.
Sunday, March 11, 2012
Deploying SMO
Hello,
I am writing a commercial client application for SQL server 2000/2005 and probably I am going to use SMO dll's.
I would like to know if there is any restriction in order to deploy SMO objects with my software. Are they free? and moreover is possible to deploy only those dll's that i actually need, without installing the whole redist package.
thank you in advance!
Zoran Maksimovic
See http://blogs.msdn.com/mwories/articles/smofaq.aspx which contains a link to the SMO redist. This page also contains limitations (but you should be generally be free to redistribute it with your application).Deploying SMO
Hello,
I am writing a commercial client application for SQL server 2000/2005 and probably I am going to use SMO dll's.
I would like to know if there is any restriction in order to deploy SMO objects with my software. Are they free? and moreover is possible to deploy only those dll's that i actually need, without installing the whole redist package.
thank you in advance!
Zoran Maksimovic
See http://blogs.msdn.com/mwories/articles/smofaq.aspx which contains a link to the SMO redist. This page also contains limitations (but you should be generally be free to redistribute it with your application).Friday, February 24, 2012
Deploy SMO project
I'm writting a tools with SMO that supports SQL Server 2005 and 2000 and I'm wondering wich components do I have to include in my setup to support both versions ?
With SQLServer 2000 my application throws a following message :
"Could not load type ‘Microsoft.sqlServer.Management.Smo.TriggerBaseCollection’ from assembly ‘Microsoft.sqlServer.Management.Smo’, version = 9.0.242.0"
Thank you.You should obtain the "Microsoft SQL Server 2005 Management Objects Collection", which contains SMO. See http://www.microsoft.com/downloads/details.aspx?FamilyID=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&DisplayLang=en
Peter
Sunday, February 19, 2012
Deploy application that uses TraceReplay and TraceFile TMO classes
Hi,
I have a .NET 2. 0 application that references SMO and uses TMO classes such as TraceReplay and TraceFile. I was under the impression that for this application to work, if SMO is installed (which means MSXML 6.0 and SQL Native Client is also installed), the application should work. But I have started to see errors like:
....Could not load file or assembly 'file:///C:\Program Files\Microsoft SQL Server\90\Tools\Binn\pfclnt90.dll' or one of its dependencies. The system cannot find the file specified.
File name: 'file:///C:\Program Files\Microsoft SQL Server\90\Tools\Binn\pfclnt90.dll'.....
and
....Could not load file or assembly 'Microsoft.SqlServer.Instapi, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies.....
SMO is installed on the machine - but it still raises the above error when TraceFile.InitializeAsReader is called.
Is anything else (in addition to SMO, MSXML 6.0, SQL Native Client) needs to be installed for TMO applications to work?
Darshan Singh
Probably too late for you, but may help others...
One thing that I recently noted that can cause the file not found for pfclnt90.dll is that the trace and replay objects are not supported on 64-bit. So if your application is running in anything other than x86 mode you get this error. A simple solution that will certainly clarify this type of issue is to compile your application for the x86 platform only, as set under project properties in Visual Studio.
(See ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/smo9mref/html/N_Microsoft_SqlServer_Management_Trace.htm)
|||The Trace and Replay objects require SQL Profiler components to be installed on the machine. Those can only be installed by full client tools installation and are not presnet in any re-dist package. We are looking into ways of removing this limiation in the future.
Regards,
Maciek Sarnowicz
Deploy application that uses TraceReplay and TraceFile TMO classes
Hi,
I have a .NET 2. 0 application that references SMO and uses TMO classes such as TraceReplay and TraceFile. I was under the impression that for this application to work, if SMO is installed (which means MSXML 6.0 and SQL Native Client is also installed), the application should work. But I have started to see errors like:
....Could not load file or assembly 'file:///C:\Program Files\Microsoft SQL Server\90\Tools\Binn\pfclnt90.dll' or one of its dependencies. The system cannot find the file specified.
File name: 'file:///C:\Program Files\Microsoft SQL Server\90\Tools\Binn\pfclnt90.dll'.....
and
....Could not load file or assembly 'Microsoft.SqlServer.Instapi, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies.....
SMO is installed on the machine - but it still raises the above error when TraceFile.InitializeAsReader is called.
Is anything else (in addition to SMO, MSXML 6.0, SQL Native Client) needs to be installed for TMO applications to work?
Darshan Singh
Probably too late for you, but may help others...
One thing that I recently noted that can cause the file not found for pfclnt90.dll is that the trace and replay objects are not supported on 64-bit. So if your application is running in anything other than x86 mode you get this error. A simple solution that will certainly clarify this type of issue is to compile your application for the x86 platform only, as set under project properties in Visual Studio.
(See ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/smo9mref/html/N_Microsoft_SqlServer_Management_Trace.htm)
|||The Trace and Replay objects require SQL Profiler components to be installed on the machine. Those can only be installed by full client tools installation and are not presnet in any re-dist package. We are looking into ways of removing this limiation in the future.
Regards,
Maciek Sarnowicz
Deploy application that uses TraceReplay and TraceFile TMO classes
Hi,
I have a .NET 2. 0 application that references SMO and uses TMO classes such as TraceReplay and TraceFile. I was under the impression that for this application to work, if SMO is installed (which means MSXML 6.0 and SQL Native Client is also installed), the application should work. But I have started to see errors like:
....Could not load file or assembly 'file:///C:\Program Files\Microsoft SQL Server\90\Tools\Binn\pfclnt90.dll' or one of its dependencies. The system cannot find the file specified.
File name: 'file:///C:\Program Files\Microsoft SQL Server\90\Tools\Binn\pfclnt90.dll'.....
and
....Could not load file or assembly 'Microsoft.SqlServer.Instapi, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies.....
SMO is installed on the machine - but it still raises the above error when TraceFile.InitializeAsReader is called.
Is anything else (in addition to SMO, MSXML 6.0, SQL Native Client) needs to be installed for TMO applications to work?
Darshan Singh
Probably too late for you, but may help others...
One thing that I recently noted that can cause the file not found for pfclnt90.dll is that the trace and replay objects are not supported on 64-bit. So if your application is running in anything other than x86 mode you get this error. A simple solution that will certainly clarify this type of issue is to compile your application for the x86 platform only, as set under project properties in Visual Studio.
(See ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/smo9mref/html/N_Microsoft_SqlServer_Management_Trace.htm)
|||The Trace and Replay objects require SQL Profiler components to be installed on the machine. Those can only be installed by full client tools installation and are not presnet in any re-dist package. We are looking into ways of removing this limiation in the future.
Regards,
Maciek Sarnowicz