<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Alternatives (and pros/cons) for techniques to control remote SM-SQL operations in Active IQ Unified Manager Discussions</title>
    <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Alternatives-and-pros-cons-for-techniques-to-control-remote-SM-SQL-operations/m-p/51403#M10618</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm involved in more than one planning effort to use WFA to control SnapManager for SQL operations on multiple Windows SQL Server systems where the customer is already a heavy SnapManager for SQL. Use cases range from a) just setting up and controlling local snapshot backups b) integrating/adding SnapMirror/Vault relationships with the servers and b) creating and presenting dev-test clones.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was going to ask here if any others have done similar things with with WFA but I find no mentions of SMSQL or SM-SQL here. &lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;In considering the underlying design choices I see several options and would be interested in hearing the pros and cons of each from others with more experience in these topics:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Use SnapManager for SQL's PowerShell cmdlets which allow a -remoteComputerName (?) option to perform a function on a remote system running SM-SQL. This would seem to require that SMSQL be installed on the WFA server itself. Can SM-SQL be installed on a Windows system that does not necessarily have MS-SQL installed on it?&lt;/LI&gt;&lt;LI&gt;Another choice would be to use remote Windows functions such as the Invoke-Command cmdlet discussed elsewhere in this community. The idea would be to use it invoke SM-SQL cmdlets on the remote systems running MS-SQL and SM-SQL. This would eliminate the need for SM-SQL on the the WFA server but may have other disadvantages.&lt;/LI&gt;&lt;LI&gt;Implement SnapCreator along side SM-SQL and use the SnapCreator Pack. I have the most questions about this since it raises several unknowns for me. For example: can SnapCreator and SM-SQL co-exist (happily or begrudgingly) on the same M-SQL server? Does SnapCreator allow the creation of clones and making them available to others hosts similar what SM-SQL can do?&amp;nbsp; &lt;/LI&gt;&lt;LI&gt;different option(s)?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm hoping these questions solicit discussion and opinions on tradeoffs and opinions on which might be the better choice in different situations.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Dave&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 05:41:35 GMT</pubDate>
    <dc:creator>korns</dc:creator>
    <dc:date>2025-06-05T05:41:35Z</dc:date>
    <item>
      <title>Alternatives (and pros/cons) for techniques to control remote SM-SQL operations</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Alternatives-and-pros-cons-for-techniques-to-control-remote-SM-SQL-operations/m-p/51403#M10618</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm involved in more than one planning effort to use WFA to control SnapManager for SQL operations on multiple Windows SQL Server systems where the customer is already a heavy SnapManager for SQL. Use cases range from a) just setting up and controlling local snapshot backups b) integrating/adding SnapMirror/Vault relationships with the servers and b) creating and presenting dev-test clones.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was going to ask here if any others have done similar things with with WFA but I find no mentions of SMSQL or SM-SQL here. &lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;In considering the underlying design choices I see several options and would be interested in hearing the pros and cons of each from others with more experience in these topics:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Use SnapManager for SQL's PowerShell cmdlets which allow a -remoteComputerName (?) option to perform a function on a remote system running SM-SQL. This would seem to require that SMSQL be installed on the WFA server itself. Can SM-SQL be installed on a Windows system that does not necessarily have MS-SQL installed on it?&lt;/LI&gt;&lt;LI&gt;Another choice would be to use remote Windows functions such as the Invoke-Command cmdlet discussed elsewhere in this community. The idea would be to use it invoke SM-SQL cmdlets on the remote systems running MS-SQL and SM-SQL. This would eliminate the need for SM-SQL on the the WFA server but may have other disadvantages.&lt;/LI&gt;&lt;LI&gt;Implement SnapCreator along side SM-SQL and use the SnapCreator Pack. I have the most questions about this since it raises several unknowns for me. For example: can SnapCreator and SM-SQL co-exist (happily or begrudgingly) on the same M-SQL server? Does SnapCreator allow the creation of clones and making them available to others hosts similar what SM-SQL can do?&amp;nbsp; &lt;/LI&gt;&lt;LI&gt;different option(s)?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm hoping these questions solicit discussion and opinions on tradeoffs and opinions on which might be the better choice in different situations.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Dave&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 05:41:35 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Alternatives-and-pros-cons-for-techniques-to-control-remote-SM-SQL-operations/m-p/51403#M10618</guid>
      <dc:creator>korns</dc:creator>
      <dc:date>2025-06-05T05:41:35Z</dc:date>
    </item>
    <item>
      <title>Re: Alternatives (and pros/cons) for techniques to control remote SM-SQL operations</title>
      <link>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Alternatives-and-pros-cons-for-techniques-to-control-remote-SM-SQL-operations/m-p/51408#M10620</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My pick would be option 2 i.e. use Invoke-Command. Its extremely useful cmdlet and has just too many advantages not to use it. You build your Posh script, run them remotely from WFA server. Disadvantages? I don't know, nothing that I have come across.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sinhaa&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 05 Mar 2014 17:59:13 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Active-IQ-Unified-Manager-Discussions/Alternatives-and-pros-cons-for-techniques-to-control-remote-SM-SQL-operations/m-p/51408#M10620</guid>
      <dc:creator>sinhaa</dc:creator>
      <dc:date>2014-03-05T17:59:13Z</dc:date>
    </item>
  </channel>
</rss>

