<?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 Re: How to force SM-SQL to create a new dataset? in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/How-to-force-SM-SQL-to-create-a-new-dataset/m-p/66224#M6901</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't think this can be done. The dataset always has a fixed name and SMSQL will use it if one exists already, or create a new one if it doesn't. Removing the dataset should not remove any volumes so you can still access the snaps, but you can't then use SMSQL to restore from them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Richard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 16 Apr 2012 12:11:20 GMT</pubDate>
    <dc:creator>rmharwood</dc:creator>
    <dc:date>2012-04-16T12:11:20Z</dc:date>
    <item>
      <title>How to force SM-SQL to create a new dataset?</title>
      <link>https://community.netapp.com/t5/Data-Protection/How-to-force-SM-SQL-to-create-a-new-dataset/m-p/66220#M6900</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can I force Sm-SQL to create a new dataset in Protection Manager? I am in a situation that I need to save the old data set for a while, but want to create a new data set.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hans&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:29:40 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/How-to-force-SM-SQL-to-create-a-new-dataset/m-p/66220#M6900</guid>
      <dc:creator>vanhees</dc:creator>
      <dc:date>2025-06-05T06:29:40Z</dc:date>
    </item>
    <item>
      <title>Re: How to force SM-SQL to create a new dataset?</title>
      <link>https://community.netapp.com/t5/Data-Protection/How-to-force-SM-SQL-to-create-a-new-dataset/m-p/66224#M6901</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't think this can be done. The dataset always has a fixed name and SMSQL will use it if one exists already, or create a new one if it doesn't. Removing the dataset should not remove any volumes so you can still access the snaps, but you can't then use SMSQL to restore from them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Richard&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Apr 2012 12:11:20 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/How-to-force-SM-SQL-to-create-a-new-dataset/m-p/66224#M6901</guid>
      <dc:creator>rmharwood</dc:creator>
      <dc:date>2012-04-16T12:11:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to force SM-SQL to create a new dataset?</title>
      <link>https://community.netapp.com/t5/Data-Protection/How-to-force-SM-SQL-to-create-a-new-dataset/m-p/66228#M6902</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Actually, I just tested this in my lab. What I did was just rename the existing data-set to "-old" or something and SM-SQL does not see a data-set anymore. After that I ran the "configuration wizard"&amp;nbsp; and SM-SQL created a new data-set. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I agree that you will not be able to restore from the old data-set using SM-SQL, this you need to do manually. But for this is enough. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hans&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Apr 2012 12:15:18 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/How-to-force-SM-SQL-to-create-a-new-dataset/m-p/66228#M6902</guid>
      <dc:creator>vanhees</dc:creator>
      <dc:date>2012-04-16T12:15:18Z</dc:date>
    </item>
  </channel>
</rss>

