Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 5987633
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 22, 20262026-05-22T22:50:36+00:00 2026-05-22T22:50:36+00:00

I inherited a SQL Server database where many tables have a primary key of

  • 0

I inherited a SQL Server database where many tables have a primary key of type numeric(18,0) .

What reasons (historical perhaps?) would someone choose this datatype for a primary key?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-22T22:50:36+00:00Added an answer on May 22, 2026 at 10:50 pm

    I would guess that the SQL Server database was originally designed in a version prior to SQL Server 2000, and this was the only way they could get an ‘integer’ bigger than the standard int. Since then, a bigint would have been more appropriate.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

SQL Server 2005 Database. I have a temporary table with many records, these records
I have inherited a SQL server database which isn't normalised and is giving me
I would like to insert a record into my SQL Server database with a
Environment: SQL Server 2005/2008, pubs database I have inserted into a table variable a
I have a local Microsoft SQL Server Compact 3.5 database (.sdf) in my WPF
I'm thinking about how to represent a complex structure in a SQL Server database.
I connect to an SQL Server 2005 DB from SAS 9.2 via SAS/Access ODBC
and once again an axapta-question ( running on ax 2009 and sql-server 2008 r2
I'm working on a .NET 4 application, C#, Entity Framework 4, SQL Server 2008.
I have an application in which I have to insert in a database, with

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.