<?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 SMSQL 5.0 discovery of new databases in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/SMSQL-5-0-discovery-of-new-databases/m-p/20232#M9934</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is the following possible?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="font-size: 12pt; color: #000000; font-family: Calibri;"&gt;We are working with SMSQL and noticed something that could be a major issue.&amp;nbsp; When we create a backup job, we select the databases to be backed up at the server level, which automatically selects all the user databases below.&amp;nbsp; Once the job is actually created, whether through the SQL agent or a scheduled task, the command actually specifies the DB’s to be backed up.&amp;nbsp; When databases are dropped or added (by the developers), it seems that SMSQL will have to be run again to cover the appropriate databases.&amp;nbsp; Is it possible to setup the jobs to just cover all the User databases without actually selecting the databases through the wizard each time a database is removed or added? &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="font-size: 12pt; color: #000000; font-family: Calibri;"&gt;--&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="font-size: 12pt; color: #000000; font-family: Calibri;"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="font-size: 12pt; color: #000000; font-family: Calibri;"&gt;Barry&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 05 Jun 2025 07:18:55 GMT</pubDate>
    <dc:creator>barryj</dc:creator>
    <dc:date>2025-06-05T07:18:55Z</dc:date>
    <item>
      <title>SMSQL 5.0 discovery of new databases</title>
      <link>https://community.netapp.com/t5/Data-Protection/SMSQL-5-0-discovery-of-new-databases/m-p/20232#M9934</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is the following possible?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="font-size: 12pt; color: #000000; font-family: Calibri;"&gt;We are working with SMSQL and noticed something that could be a major issue.&amp;nbsp; When we create a backup job, we select the databases to be backed up at the server level, which automatically selects all the user databases below.&amp;nbsp; Once the job is actually created, whether through the SQL agent or a scheduled task, the command actually specifies the DB’s to be backed up.&amp;nbsp; When databases are dropped or added (by the developers), it seems that SMSQL will have to be run again to cover the appropriate databases.&amp;nbsp; Is it possible to setup the jobs to just cover all the User databases without actually selecting the databases through the wizard each time a database is removed or added? &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="font-size: 12pt; color: #000000; font-family: Calibri;"&gt;--&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="font-size: 12pt; color: #000000; font-family: Calibri;"&gt;Thanks,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="font-size: 12pt; color: #000000; font-family: Calibri;"&gt;Barry&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:18:55 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SMSQL-5-0-discovery-of-new-databases/m-p/20232#M9934</guid>
      <dc:creator>barryj</dc:creator>
      <dc:date>2025-06-05T07:18:55Z</dc:date>
    </item>
    <item>
      <title>Re: SMSQL 5.0 discovery of new databases</title>
      <link>https://community.netapp.com/t5/Data-Protection/SMSQL-5-0-discovery-of-new-databases/m-p/20236#M9935</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My experience so far is the same. The only way one can recognize the new db's is to run the snapmanger sqlserver configuration one more time.&lt;/P&gt;&lt;P&gt;It would be nice to have a feature where we do not need to but i guess there is no other way to let the tool know that a new db has been added.&lt;/P&gt;&lt;P&gt;Alos every time new db is added one has to delete the job from sqlagent and recreate a new job as simply edition of the existing won't work too.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Feb 2010 17:00:38 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SMSQL-5-0-discovery-of-new-databases/m-p/20236#M9935</guid>
      <dc:creator>gtadimalla</dc:creator>
      <dc:date>2010-02-24T17:00:38Z</dc:date>
    </item>
    <item>
      <title>Re: SMSQL 5.0 discovery of new databases</title>
      <link>https://community.netapp.com/t5/Data-Protection/SMSQL-5-0-discovery-of-new-databases/m-p/20241#M9936</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="font-family: Courier New; color: #000000;"&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;In this scenario where all databases in a particular SQL Server instance are being backed up the following option is available: -&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;1. Go to the Windows task manager or Sql Server Agent (depending on where the backup job has been scheduled).&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;2. Edit the command that is run and just use the server name. For example if the SQL Server host name is SNAPMGR and the instance name is INST1 then the command should look like:- &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: Courier New;"&gt;&lt;SPAN style="color: #000000;"&gt;&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="mso-spacerun: yes;"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;SPAN style="color: #000000; font-family: Courier New; "&gt;&lt;SPAN style="mso-spacerun: yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;new-backup –svr 'SNAPMGR'&lt;SPAN style="mso-spacerun: yes;"&gt;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;-d&lt;SPAN style="mso-spacerun: yes;"&gt;&amp;nbsp; &lt;/SPAN&gt;'SNAPMGR\INST1', '0'&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;SPAN style="font-family: 'Courier New'; "&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="MsoPlainText"&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/SPAN&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt; mso-layout-grid-align: none;"&gt;&lt;SPAN style="mso-no-proof: yes; color: #000000; font-size: 10pt; font-family: Arial; "&gt;Sourav Chakraborty&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt; mso-layout-grid-align: none;"&gt;&lt;SPAN style="mso-no-proof: yes; color: #000000; font-size: 12pt; font-family: Arial; "&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt; mso-layout-grid-align: none;"&gt;&lt;SPAN style="mso-no-proof: yes; color: #000000; font-size: 10pt; font-family: Arial; "&gt;Technical Marketing Engineer &lt;BR /&gt;SMAI , NetApp&lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoNormal" style="margin: 0in 0in 0pt; mso-layout-grid-align: none;"&gt;&lt;SPAN style="mso-no-proof: yes; color: #000000; font-size: 10pt; font-family: Arial; "&gt; &lt;/SPAN&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;/P&gt;&lt;P class="MsoPlainText" style="margin: 0in 0in 0pt;"&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Mar 2010 15:47:02 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SMSQL-5-0-discovery-of-new-databases/m-p/20241#M9936</guid>
      <dc:creator>sourav</dc:creator>
      <dc:date>2010-03-01T15:47:02Z</dc:date>
    </item>
    <item>
      <title>Re: SMSQL 5.0 discovery of new databases</title>
      <link>https://community.netapp.com/t5/Data-Protection/SMSQL-5-0-discovery-of-new-databases/m-p/20249#M9937</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Sourav, we will give this a try.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Barry&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Mar 2010 15:49:26 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SMSQL-5-0-discovery-of-new-databases/m-p/20249#M9937</guid>
      <dc:creator>barryj</dc:creator>
      <dc:date>2010-03-01T15:49:26Z</dc:date>
    </item>
  </channel>
</rss>

