Drop Table

Support Forum for database administrators and web based access to important newsgroups related to databases
Register on Database Support Forum Edit your profileCalendarFind other Database Support forum membersFrequently Asked QuestionsSearch this forum -> 
For Database admins: Free Database-related Magazines Now Free shipping to Texas


Post New Thread










Thread
Author

Converting INT datatype to BIGINT datatype
HI,

I have a table with IDENTITY column with the datatype as INTEGER. Now
this table record count is almost reaching  its limt. that is total
record count is almost near to 2^31-1. It will reach the limit with in
another one or two months.

In order to avoid the arithmentic overflow error 8115, we would like
change the datatype from INT to BIGINT. we hope this will solve our
problem.

How do I approch this datatype conversion?. Since the data count is
huge, that leads to a long down time of database.

we need better approach or solution for this problem?. kindly give me
a better solution that will reduce the total downtime of the production
database.?.

Regards


Report this thread to moderator Post Follow-up to this message
Old Post
Praveen
12-15-05 12:23 PM


Re: Converting INT datatype to BIGINT datatype
Please don't multi-post.  I answered this in the MS newsgroups.

--
Tom

----------------------------------------------------
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON   Canada
www.pinpub.com
.
"Praveen" <apveen@gmail.com> wrote in message
news:1134646404.601029.41010@o13g2000cwo.googlegroups.com...
HI,

I have a table with IDENTITY column with the datatype as INTEGER. Now
this table record count is almost reaching  its limt. that is total
record count is almost near to 2^31-1. It will reach the limit with in
another one or two months.

In order to avoid the arithmentic overflow error 8115, we would like
change the datatype from INT to BIGINT. we hope this will solve our
problem.

How do I approch this datatype conversion?. Since the data count is
huge, that leads to a long down time of database.

we need better approach or solution for this problem?. kindly give me
a better solution that will reduce the total downtime of the production
database.?.

Regards


Report this thread to moderator Post Follow-up to this message
Old Post
Tom Moreau
12-15-05 12:23 PM


Sponsored Links





Last Thread Next Thread
Post New Thread

Microsoft SQL Server forum archive

Show a Printable Version Email This Page to Someone! Receive updates to this thread
Microsoft SQL Server
Access database support
PostgreSQL Replication
SQL Server ODBC
FoxPro Support
PostgreSQL pgAdmin
SQL Server Clustering
MySQL ODBC
Web Applications with dBASE
SQL Server CE
MySQL++
Sybase Database Support
MS SQL Full Text Search
PostgreSQL Administration
SQL Anywhere support
DB2 UDB Database
Paradox Database Support
Filemaker Database
Berkley DB
SQL 2000/2000i database
ASE Database
Forum Jump:
All times are GMT. The time now is 11:22 PM.

 
Mobile devices forum | Database support forum archive




Copyrights DropTable.com Database Support Forum 2004 - 2006