<?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: Connect SQL Server 2008 to SAS with ODBC in SAS Studio</title>
    <link>https://communities.sas.com/t5/SAS-Studio/Connect-SQL-Server-2008-to-SAS-with-ODBC/m-p/309763#M1466</link>
    <description>&lt;P&gt;Checked with my DBA this morning and we still have lots of stray connections.&amp;nbsp; The person who signed on has a connection to a test database he never even uses&amp;nbsp; We have large statisticl modeling jobs that run overnight, so closing SAS workspace might be a little dicey for us.&amp;nbsp; I'm wondering about the "Whether to automatically drop utility connections" option?&amp;nbsp;&amp;nbsp; I'll do some more research.&lt;/P&gt;</description>
    <pubDate>Mon, 07 Nov 2016 16:28:31 GMT</pubDate>
    <dc:creator>AnnBlakeslee</dc:creator>
    <dc:date>2016-11-07T16:28:31Z</dc:date>
    <item>
      <title>Connect SQL Server 2008 to SAS with ODBC</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Connect-SQL-Server-2008-to-SAS-with-ODBC/m-p/308399#M1408</link>
      <description>&lt;P&gt;I've got SQL Server tables set up in Metadata and they work fine. &amp;nbsp;The trouble is, my SQL Server DBA is complaining that we have dozens of apparently "orphaned" SQL Server processes that are left by the users of SAS Studio. &amp;nbsp;How do I make SAS Studio clean up the connections? &amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 31 Oct 2016 23:12:35 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Connect-SQL-Server-2008-to-SAS-with-ODBC/m-p/308399#M1408</guid>
      <dc:creator>AnnBlakeslee</dc:creator>
      <dc:date>2016-10-31T23:12:35Z</dc:date>
    </item>
    <item>
      <title>Re: Connect SQL Server 2008 to SAS with ODBC</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Connect-SQL-Server-2008-to-SAS-with-ODBC/m-p/308405#M1410</link>
      <description>&lt;P&gt;How are your SQL Server data sources set up in metadata - are they pre-assigned or not? If they are pre-assigned you should also add the defer = yes option so database connections are only created if the data source is opened.&lt;/P&gt;</description>
      <pubDate>Tue, 01 Nov 2016 00:41:07 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Connect-SQL-Server-2008-to-SAS-with-ODBC/m-p/308405#M1410</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2016-11-01T00:41:07Z</dc:date>
    </item>
    <item>
      <title>Re: Connect SQL Server 2008 to SAS with ODBC</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Connect-SQL-Server-2008-to-SAS-with-ODBC/m-p/308545#M1417</link>
      <description>Sounds logical. Let me give it a shot! Do I need to restart the SAS&lt;BR /&gt;Connect Server to make this option kick in?&lt;BR /&gt;&lt;BR /&gt;##- Please type your reply above this line. Simple formatting, no&lt;BR /&gt;attachments. -##&lt;BR /&gt;Ann Blakeslee&lt;BR /&gt;Institute for Health Research (IHR)&lt;BR /&gt;(303) 614-1359&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;NOTICE TO RECIPIENT: If you are not the intended recipient of this&lt;BR /&gt;e-mail, you are prohibited from sharing, copying, or otherwise using or&lt;BR /&gt;disclosing its contents. If you have received this e-mail in error,&lt;BR /&gt;please notify the sender immediately by reply e-mail and permanently&lt;BR /&gt;delete this e-mail and any attachments without reading, forwarding or&lt;BR /&gt;saving them. Thank you.</description>
      <pubDate>Tue, 01 Nov 2016 15:26:57 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Connect-SQL-Server-2008-to-SAS-with-ODBC/m-p/308545#M1417</guid>
      <dc:creator>AnnBlakeslee</dc:creator>
      <dc:date>2016-11-01T15:26:57Z</dc:date>
    </item>
    <item>
      <title>Re: Connect SQL Server 2008 to SAS with ODBC</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Connect-SQL-Server-2008-to-SAS-with-ODBC/m-p/308601#M1427</link>
      <description>&lt;P&gt;No. Just disconnecting your workspace SAS session and reconnecting should do the trick. You may want to check with your SQL Server DBA as well to see if there is a server connection timeout he can set. I'd suggest something like 24 hours.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Where I work we close all SAS workspace sessions at 2am so we can replicate our SAS environment. This will also drop all database connections.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 01 Nov 2016 19:14:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Connect-SQL-Server-2008-to-SAS-with-ODBC/m-p/308601#M1427</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2016-11-01T19:14:39Z</dc:date>
    </item>
    <item>
      <title>Re: Connect SQL Server 2008 to SAS with ODBC</title>
      <link>https://communities.sas.com/t5/SAS-Studio/Connect-SQL-Server-2008-to-SAS-with-ODBC/m-p/309763#M1466</link>
      <description>&lt;P&gt;Checked with my DBA this morning and we still have lots of stray connections.&amp;nbsp; The person who signed on has a connection to a test database he never even uses&amp;nbsp; We have large statisticl modeling jobs that run overnight, so closing SAS workspace might be a little dicey for us.&amp;nbsp; I'm wondering about the "Whether to automatically drop utility connections" option?&amp;nbsp;&amp;nbsp; I'll do some more research.&lt;/P&gt;</description>
      <pubDate>Mon, 07 Nov 2016 16:28:31 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Studio/Connect-SQL-Server-2008-to-SAS-with-ODBC/m-p/309763#M1466</guid>
      <dc:creator>AnnBlakeslee</dc:creator>
      <dc:date>2016-11-07T16:28:31Z</dc:date>
    </item>
  </channel>
</rss>

