title: SQL Server: store INT in BIGINT column can be a problem?
body: <p>I have mapping table in the following structure:</p>
  
  <pre><code>CREATE TABLE MappingTable 
  (
      TableName SYSNAME,
      SrcId BIGINT,
      DstId BIGINT,
      PRIMARY KEY (Name, SrcId),
      UNIQUE (Name, DstId)
  )
  </code></pre>
  
  <p><code>SrcId</code> and <code>DstId</code> are referring to <code>Identity</code> columns in 2 identical databases, most of the columns type is <code>INT</code> but some are <code>BIGINT</code>, therefore I am storing all as <code>BIGINT</code>.</p>
  
  <p>Now I want to write function to get <code>DstId</code> for <code>TableName</code> and <code>SrcId</code>. </p>
  
  <p>So my question is simple: do I have any reason to implement 2 functions, one for <code>INT</code> and the 2nd for <code>BIGINT</code>? </p>
  
  <p>To clarify: I read what I'd wrote: when an <code>INT</code> was written it reads as <code>INT</code>, and the same is for <code>BIGINT</code>.</p>