Max limit of Auto

May i know what is the MAX number Auto ID can go in a table for SQL server
'Depends on your datatype you use. Check out the capacities of the datatypes
INT, BIGINT, Decimal etc. in BooksOnLine.
--
Andrew J. Kelly SQL MVP
"Cason" <Cason@.cason.com> wrote in message
news:uie9yplAEHA.3352@.TK2MSFTNGP09.phx.gbl...
> May i know what is the MAX number Auto ID can go in a table for SQL server
> '
>|||A column with the IDENTITY property is limited only by the precision of the
underlying data type:
tinyint=127
smallint-32767
int=2147483647
bigint=9223372036854775807
decimal(38)=99999999999999999999999999999999999999
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Cason" <Cason@.cason.com> wrote in message
news:uie9yplAEHA.3352@.TK2MSFTNGP09.phx.gbl...
> May i know what is the MAX number Auto ID can go in a table for SQL server
> '
>|||Hi,
That depends up on the data type for which the column is associated.
Maximum limit for an autoid (Identity) is 2 power 63 that is
9,223,372,036,854,775,807. For this the data type should be BIGINT.
The below datypes are supported for Autoid (Identity)
1. Tinyint
2. Smallint
3. int
4. Bigint
1. Numeric
2. decimal
For Numeric and decimal scale shoule be '0' and it allows a maximum of
Numeric(38,0)
Thanks
Hari
MCDBA
"Cason" <Cason@.cason.com> wrote in message
news:uie9yplAEHA.3352@.TK2MSFTNGP09.phx.gbl...
> May i know what is the MAX number Auto ID can go in a table for SQL server
> '
>|||If you are speaking of an Identity column, it depends on the underlying data
type. if you use a bigint datatype with an identity with a seed and
increment of 1 then the maximum positive number is 9223372036854775808. If
you are looking at womething like a uniqueidentifier (GUID) I believe this
is unlimited...
Neil MacMurchy
Senior DBA
Regional Municipality of Niagara
"Cason" <Cason@.cason.com> wrote in message
news:uie9yplAEHA.3352@.TK2MSFTNGP09.phx.gbl...
> May i know what is the MAX number Auto ID can go in a table for SQL server
> '
>|||If under "Auto ID" you mean IDENTITY then it depends on the column's data
type.
For bigint:
Integer (whole number) data from -2^63 (-9,223,372,036,854,775,808) through
2^63-1 (9,223,372,036,854,775,807). Storage size is 8 bytes.
For decimal:
Fixed precision and scale numbers. When maximum precision is used, valid
values are from - 10^38 +1 through 10^38 - 1.
HTH
Igor Raytsin
"Cason" <Cason@.cason.com> wrote in message
news:uie9yplAEHA.3352@.TK2MSFTNGP09.phx.gbl...
> May i know what is the MAX number Auto ID can go in a table for SQL server
> '
>

Max limit of Auto

May i know what is the MAX number Auto ID can go in a table for SQL server
'Depends on your datatype you use. Check out the capacities of the datatypes
INT, BIGINT, Decimal etc. in BooksOnLine.
Andrew J. Kelly SQL MVP
"Cason" <Cason@.cason.com> wrote in message
news:uie9yplAEHA.3352@.TK2MSFTNGP09.phx.gbl...
> May i know what is the MAX number Auto ID can go in a table for SQL server
> '
>|||A column with the IDENTITY property is limited only by the precision of the
underlying data type:
tinyint=127
smallint-32767
int=2147483647
bigint=9223372036854775807
decimal(38)=9999999999999999999999999999
9999999999
Hope this helps.
Dan Guzman
SQL Server MVP
"Cason" <Cason@.cason.com> wrote in message
news:uie9yplAEHA.3352@.TK2MSFTNGP09.phx.gbl...
> May i know what is the MAX number Auto ID can go in a table for SQL server
> '
>|||Hi,
That depends up on the data type for which the column is associated.
Maximum limit for an autoid (Identity) is 2 power 63 that is
9,223,372,036,854,775,807. For this the data type should be BIGINT.
The below datypes are supported for Autoid (Identity)
1. Tinyint
2. Smallint
3. int
4. Bigint
1. Numeric
2. decimal
For Numeric and decimal scale shoule be '0' and it allows a maximum of
Numeric(38,0)
Thanks
Hari
MCDBA
"Cason" <Cason@.cason.com> wrote in message
news:uie9yplAEHA.3352@.TK2MSFTNGP09.phx.gbl...
> May i know what is the MAX number Auto ID can go in a table for SQL server
> '
>|||If you are speaking of an Identity column, it depends on the underlying data
type. if you use a bigint datatype with an identity with a seed and
increment of 1 then the maximum positive number is 9223372036854775808. If
you are looking at womething like a uniqueidentifier (GUID) I believe this
is unlimited...
Neil MacMurchy
Senior DBA
Regional Municipality of Niagara
"Cason" <Cason@.cason.com> wrote in message
news:uie9yplAEHA.3352@.TK2MSFTNGP09.phx.gbl...
> May i know what is the MAX number Auto ID can go in a table for SQL server
> '
>|||If under "Auto ID" you mean IDENTITY then it depends on the column's data
type.
For bigint:
Integer (whole number) data from -2^63 (-9,223,372,036,854,775,808) through
2^63-1 (9,223,372,036,854,775,807). Storage size is 8 bytes.
For decimal:
Fixed precision and scale numbers. When maximum precision is used, valid
values are from - 10^38 +1 through 10^38 - 1.
HTH
Igor Raytsin
"Cason" <Cason@.cason.com> wrote in message
news:uie9yplAEHA.3352@.TK2MSFTNGP09.phx.gbl...
> May i know what is the MAX number Auto ID can go in a table for SQL server
> '
>

Max Connections?

Hi,
We're frequently getting a 'Timeout Expired' error on ASP pages that access
one of our SQL database servers. Is there a limit to the number of
concurrent connections with SQL server 2000 or has anyone else experienced
this behaviour? It is becoming quite frequent (around once a day). The only
thing that seems to solve it is a restart of the SQL services.
Thanks for any assistance - Ian
"Ian Bell" <ianbell6862@.hotmail.comm> wrote in
news:uva#C1vSFHA.3392@.TK2MSFTNGP12.phx.gbl:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that
> access one of our SQL database servers. Is there a limit to the number
> of concurrent connections with SQL server 2000 or has anyone else
> experienced this behaviour? It is becoming quite frequent (around once
> a day). The only thing that seems to solve it is a restart of the SQL
> services.
> Thanks for any assistance - Ian
>
See FAQ for limited connections in IIS. Review your ASP code.
http://www.microsoft.com/technet/com...si1203.mspx#EB
AA
Regards
JTC ^..^
|||According to this article there is not a limit to the number of concurrent
connections with SQL server databases.
http://msdn.microsoft.com/library/de...r_sa2_0ciq.asp
"Ian Bell" wrote:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>
|||According to this article there is not a limit to concurrent connections in
SQL Server 2000.
http://msdn.microsoft.com/library/de...r_sa2_0ciq.asp
You might want to check the setting for multiple connections in your website
settings in IIS.
"Ian Bell" wrote:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>

Max Connections?

Hi,
We're frequently getting a 'Timeout Expired' error on ASP pages that access
one of our SQL database servers. Is there a limit to the number of
concurrent connections with SQL server 2000 or has anyone else experienced
this behaviour? It is becoming quite frequent (around once a day). The only
thing that seems to solve it is a restart of the SQL services.
Thanks for any assistance - Ian"Ian Bell" <ianbell6862@.hotmail.comm> wrote in
news:uva#C1vSFHA.3392@.TK2MSFTNGP12.phx.gbl:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that
> access one of our SQL database servers. Is there a limit to the number
> of concurrent connections with SQL server 2000 or has anyone else
> experienced this behaviour? It is becoming quite frequent (around once
> a day). The only thing that seems to solve it is a restart of the SQL
> services.
> Thanks for any assistance - Ian
>
See FAQ for limited connections in IIS. Review your ASP code.
http://www.microsoft.com/technet/co...isi1203.mspx#EB
AA
Regards
JTC ^..^|||According to this article there is not a limit to the number of concurrent
connections with SQL server databases.
_0ciq.asp" target="_blank">http://msdn.microsoft.com/library/d...r />
_0ciq.asp
"Ian Bell" wrote:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that acces
s
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The onl
y
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>|||According to this article there is not a limit to concurrent connections in
SQL Server 2000.
_0ciq.asp" target="_blank">http://msdn.microsoft.com/library/d...r />
_0ciq.asp
You might want to check the setting for multiple connections in your website
settings in IIS.
"Ian Bell" wrote:

> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that acces
s
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The onl
y
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>

Max Connections?

Hi,
We're frequently getting a 'Timeout Expired' error on ASP pages that access
one of our SQL database servers. Is there a limit to the number of
concurrent connections with SQL server 2000 or has anyone else experienced
this behaviour? It is becoming quite frequent (around once a day). The only
thing that seems to solve it is a restart of the SQL services.
Thanks for any assistance - Ian"Ian Bell" <ianbell6862@.hotmail.comm> wrote in
news:uva#C1vSFHA.3392@.TK2MSFTNGP12.phx.gbl:
> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that
> access one of our SQL database servers. Is there a limit to the number
> of concurrent connections with SQL server 2000 or has anyone else
> experienced this behaviour? It is becoming quite frequent (around once
> a day). The only thing that seems to solve it is a restart of the SQL
> services.
> Thanks for any assistance - Ian
>
See FAQ for limited connections in IIS. Review your ASP code.
http://www.microsoft.com/technet/community/columns/insider/iisi1203.mspx#EB
AA
--
Regards
JTC ^..^|||According to this article there is not a limit to the number of concurrent
connections with SQL server databases
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa2_0ciq.asp
"Ian Bell" wrote:
> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>|||According to this article there is not a limit to concurrent connections in
SQL Server 2000.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa2_0ciq.asp
You might want to check the setting for multiple connections in your website
settings in IIS.
"Ian Bell" wrote:
> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>sql