<?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 Stored Procedure with Data Parameters (Enter Date Parameters before Query Refresh) in Developer</title>
    <link>https://community.fabric.microsoft.com/t5/Developer/SQL-Server-Stored-Procedure-with-Data-Parameters-Enter-Date/m-p/1195646#M24500</link>
    <description>&lt;P&gt;I have a stored procedure that asks for dates before running the query.&amp;nbsp; Is there a way to have a query run inside PowerBI and before it actually runs asks for specific date parameters?&amp;nbsp; Issue is the data size.&amp;nbsp; We dont want them running a large query and the date will be changing daily.&amp;nbsp; Basically want to see if BI can have parameters like SSRS before a query runs.&amp;nbsp; Any info would be helpful.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 01 Jul 2020 16:28:13 GMT</pubDate>
    <dc:creator>common763</dc:creator>
    <dc:date>2020-07-01T16:28:13Z</dc:date>
    <item>
      <title>SQL Server Stored Procedure with Data Parameters (Enter Date Parameters before Query Refresh)</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/SQL-Server-Stored-Procedure-with-Data-Parameters-Enter-Date/m-p/1195646#M24500</link>
      <description>&lt;P&gt;I have a stored procedure that asks for dates before running the query.&amp;nbsp; Is there a way to have a query run inside PowerBI and before it actually runs asks for specific date parameters?&amp;nbsp; Issue is the data size.&amp;nbsp; We dont want them running a large query and the date will be changing daily.&amp;nbsp; Basically want to see if BI can have parameters like SSRS before a query runs.&amp;nbsp; Any info would be helpful.&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2020 16:28:13 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/SQL-Server-Stored-Procedure-with-Data-Parameters-Enter-Date/m-p/1195646#M24500</guid>
      <dc:creator>common763</dc:creator>
      <dc:date>2020-07-01T16:28:13Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Server Stored Procedure with Data Parameters (Enter Date Parameters before Query Refresh)</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/SQL-Server-Stored-Procedure-with-Data-Parameters-Enter-Date/m-p/1196002#M24505</link>
      <description>&lt;P&gt;Yes, you can parameterize your query in a lot of flexible ways.&amp;nbsp; However, very soon you will hit a wall, namely the Formula:Firewall. Best read up on privacy levels and combining queries from different sources (which is basically what you'll be doing).&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2020 20:18:16 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/SQL-Server-Stored-Procedure-with-Data-Parameters-Enter-Date/m-p/1196002#M24505</guid>
      <dc:creator>lbendlin</dc:creator>
      <dc:date>2020-07-01T20:18:16Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Server Stored Procedure with Data Parameters (Enter Date Parameters before Query Refresh)</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/SQL-Server-Stored-Procedure-with-Data-Parameters-Enter-Date/m-p/1196030#M24511</link>
      <description>&lt;P&gt;So let me ask a different way because maybe there is an alternate approach.&amp;nbsp; If I have a dataset from SQL, where the end user could want any random start end date and the actual query or stored procedure is too large to refresh everytime it is run (without a smaller date range), what is a good easy solution that would somehow replicate what SSRS does when a report opens and the end-user selects two dates, then it goes out and gets the data?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2020 20:36:01 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/SQL-Server-Stored-Procedure-with-Data-Parameters-Enter-Date/m-p/1196030#M24511</guid>
      <dc:creator>common763</dc:creator>
      <dc:date>2020-07-01T20:36:01Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Server Stored Procedure with Data Parameters (Enter Date Parameters before Query Refresh)</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/SQL-Server-Stored-Procedure-with-Data-Parameters-Enter-Date/m-p/1196032#M24512</link>
      <description>&lt;P&gt;That would be called a Direct Query connection.&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2020 20:37:34 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/SQL-Server-Stored-Procedure-with-Data-Parameters-Enter-Date/m-p/1196032#M24512</guid>
      <dc:creator>lbendlin</dc:creator>
      <dc:date>2020-07-01T20:37:34Z</dc:date>
    </item>
    <item>
      <title>Re: SQL Server Stored Procedure with Data Parameters (Enter Date Parameters before Query Refresh)</title>
      <link>https://community.fabric.microsoft.com/t5/Developer/SQL-Server-Stored-Procedure-with-Data-Parameters-Enter-Date/m-p/1198092#M24530</link>
      <description>&lt;P&gt;This makes sense and is simple so appreciate it.&amp;nbsp; I will take this approach and see how it works for me.&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jul 2020 13:29:05 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Developer/SQL-Server-Stored-Procedure-with-Data-Parameters-Enter-Date/m-p/1198092#M24530</guid>
      <dc:creator>common763</dc:creator>
      <dc:date>2020-07-02T13:29:05Z</dc:date>
    </item>
  </channel>
</rss>

