title: One data set returns null for one user only on SSRS 2008
body: <p>I am experiencing an odd situation. I have a production and test report server up and running and they have been running flawlessly for over a year. On Monday 5/20 everything was working. Beginning yesterday I began to experience a data set returning <code>NULL</code> for one user only. I have access to two domain users, one we will call <code>name</code> and one we will call <code>db</code>. The <code>name</code> user is my normal user and is what I log on to my PC with. The <code>db</code> user is the one I use for development tasks and troubleshooting. The <code>db</code> user is the one affected.</p>
  
  <p>The data set in question is a very simple two line SQL select that list the company's branches for use in various reports on the report server. Here is a generic representation of that query:</p>
  
  <pre><code>select branchID, branchName from branch
  </code></pre>
  
  <p>This query runs in SQL Server Management Studio. Here are the things I have done to verify the scope of the issue:</p>
  
  <p>I logged on to the production and development report servers with <code>name</code> and ran <code>Report X</code> that depends on the <code>branch</code> data set. The report output was correct.</p>
  
  <p>I logged on to the production and development report servers with <code>db</code> and ran <code>Report X</code> and could not select a branch because no values were present in the Branch combo box.</p>
  
  <p>I opened the data set in Report Builder 3.0 and executed it on both users. The <code>name</code> user got the correct result set back but the <code>db</code> user did not.</p>
  
  <p>I asked a couple of users that I trust to run <code>Report X</code> and it ran fine for them.</p>
  
  <p>I asked my network admin to double check domain permissions for <code>db</code> and they looked fine.</p>
  
  <p>I double checked the ODBC driver I use for the report server and the connection is good.</p>
  
  <p>I am at a loss as to what to check. Any suggestions?</p>
  
  <p><strong>Edit 1: I also ran <code>Report Y</code> with the <code>db</code> user. This report does not use the branch data set and it ran fine. The only data set that has an issue is the branch data set.</strong></p>
  
  <p><strong>Edit 2: I logged on to SSMS with the problem user and ran select * from branch and the result set was empty. In addition I ran select * from equipment and the result set was valid - around 54,000 records. So it appears to be a permission issue on some tables. The only one I know about is the branch table.</strong></p>