<?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 SQL Server (Vector instead of Raster) in ArcMap Questions</title>
    <link>https://community.esri.com/t5/arcmap-questions/sql-server-vector-instead-of-raster/m-p/1005789#M1650</link>
    <description>&lt;P&gt;Hi dear Friends,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;recently I came across to a peculiar phenomenon and I want to share my Experience with you. So it might help you save time.&amp;nbsp;&lt;/P&gt;&lt;P&gt;In our Organization we upgraded our SQL Server to 2019 and after that as I tried to import my Raster with this tool (Raster to Geodatabase) I got a &lt;STRONG&gt;vector&lt;/STRONG&gt;-Dataset instead of Raster-Dataset.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This Phenomenon can happen when you not enough RAM in your Server installed. So be Careful to check the RAM available in your Server.&amp;nbsp; Because when you try to import a big data such as raster data. You are going to save the converted table in your RAM and after that the Whole data in your SQL Data bank.&amp;nbsp; This approach will save you a lot of time dealing with damaged Raster, because there will&amp;nbsp; be no need to delete them from Server.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Although I couldn't understand why instead of an error for lack of RAM I got a vector dataset.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Stay Healthy&amp;nbsp;&lt;/P&gt;&lt;P&gt;ko.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 01 Dec 2020 08:15:55 GMT</pubDate>
    <dc:creator>KouroshArjmand</dc:creator>
    <dc:date>2020-12-01T08:15:55Z</dc:date>
    <item>
      <title>SQL Server (Vector instead of Raster)</title>
      <link>https://community.esri.com/t5/arcmap-questions/sql-server-vector-instead-of-raster/m-p/1005789#M1650</link>
      <description>&lt;P&gt;Hi dear Friends,&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;recently I came across to a peculiar phenomenon and I want to share my Experience with you. So it might help you save time.&amp;nbsp;&lt;/P&gt;&lt;P&gt;In our Organization we upgraded our SQL Server to 2019 and after that as I tried to import my Raster with this tool (Raster to Geodatabase) I got a &lt;STRONG&gt;vector&lt;/STRONG&gt;-Dataset instead of Raster-Dataset.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This Phenomenon can happen when you not enough RAM in your Server installed. So be Careful to check the RAM available in your Server.&amp;nbsp; Because when you try to import a big data such as raster data. You are going to save the converted table in your RAM and after that the Whole data in your SQL Data bank.&amp;nbsp; This approach will save you a lot of time dealing with damaged Raster, because there will&amp;nbsp; be no need to delete them from Server.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Although I couldn't understand why instead of an error for lack of RAM I got a vector dataset.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Stay Healthy&amp;nbsp;&lt;/P&gt;&lt;P&gt;ko.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Dec 2020 08:15:55 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcmap-questions/sql-server-vector-instead-of-raster/m-p/1005789#M1650</guid>
      <dc:creator>KouroshArjmand</dc:creator>
      <dc:date>2020-12-01T08:15:55Z</dc:date>
    </item>
  </channel>
</rss>

