title: Cross Database Stored Procedure performance considerations
body: <p>In my project I have two separate DBs on the same server. The DBs are self-sufficient except for three columns in DB "B" that need to be accessed in DB "A".</p>
  
  <p>Are there performance considerations if I were to have a stored proc in A that accessed three columns from B directly?</p>
  
  <p>Currently, we run a nightly job to import the needed data from table B to table A, so that the stored proc isn't going out of the scope of A.</p>
  
  <p>Is that the best method? </p>
  
  <p>Are cross DB stored procs within best practices?</p>