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 551673
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 13, 20262026-05-13T11:25:08+00:00 2026-05-13T11:25:08+00:00

Currently my application is 32-bit. This means that all tables running on SQL Server

  • 0

Currently my application is 32-bit.

This means that all tables running on SQL Server 2008 IDs’ are INT that is equal to System.Int32 and everywhere where I parse strings to integers, I use Int32.TryParse().

I called this Implicit int size indication.

If I will want to make my application to be 64-bit I think there will be 2 scenarios:

  • Rename all Int32 to Int64 and INT to BIGINT.

or

  • Rename all Int32 to int NOW and make int size indication be Explicit.

Which is better, how do you think?

  • 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-13T11:25:08+00:00Added an answer on May 13, 2026 at 11:25 am

    C# and SQL Server both have fixed size of integers on all platforms. int in C# (which is simply an alias for System.Int32 structure) and SQL Server is always 32 bits. Similarly, long in C# (an alias for System.Int64 structure and SQL Server’s bigint are always 64 bits regardless of the platform.

    In C#, it’s more natural to use the language defined alias for types (int instead of Int32, long instead of Int64) except for public method names (ReadInt64 is preferable to ReadLong) as the method might be used in a language without or with different type aliases and it’s better to use the .NET Framework name instead of the C# alias.

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

Sidebar

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.