max no. of values in WHERE ... IN clause

Hi all,

can anyone tell mey what the maximum number of values (if there is any) which can be used in the WHERE ... IN clause?

ex:
... WHERE ID IN (1, 2, 3 ... , n) ...
what is the maximum number of values which I can put between paranthesis?

10x in advance
mihai.That's decided by the specific DB system.|||10x in advance

"10X" = "thanks"? Whatever next...!|||How many can you put there is one question. How many can you put there and still get an answer while you are young enough to care is a different question. The answer to both questions varies significantly from one query and database engine to another.

-PatP

max no of datafiles

whats the maximum no of datafiles & logfiles sqlserver
supports.
thanksFrom BOL
32,767 files per database
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"kumar" <sqldba2004@.yahoo.com> wrote in message
news:149c401c414cd$7f963c60$a301280a@.phx
.gbl...
> whats the maximum no of datafiles & logfiles sqlserver
> supports.
> thanks

Max mirroring DB on a 64-bit sysstem?

According to BOL we know

"On a 32-bit system, database mirroring can support a maximum of about 10 databases per server instance because of the numbers of worker threads that are consumed by each database mirroring session."

My question is: What is maximum number of mirrored DB we can deploy on 64-bit system per one sql instance?

It depends. Do you have a 64-CPU box with 1 TB of RAM or a 4 CPU box with 4 GB? The variety of 64-bit hardware available makes specific guidance difficult.

You will need to test your configuration appropriately regardless.

|||

Peter thanks for you answer.

We have got the next configuration :

HP Superdome (1 cell) 4 CPU?(Dual core Itanium 2 1.6GHz, 24 MB Cache),?32GB.

|||

In the case of multiple databases, I use a different tack to overcome the problem. If I find any database failed over, I run SQL commands to fail them all over. "ALTER DATABASE [dbname] SET PARTNER FAILOVER" you must proceed the command with "USE [master]". It works in my case as i am running web code against multiple databases at any given point in time, so I have to have them all failover at the same time anyways. The statement to return the state of each database is "SELECT * from sys.database_mirroring WHERE mirroring_guid IS NOT NULL" I read the values programatically and run the appropriate failover statements depending on the values returned.

|||This was extremely useful, I copied it verbatim into a scheduled task that runs every minute and checks this, because we've had the same issue where only some but not all databases fail over. There should be an SQL Server feature to make multiple databases "atomic" for the purpose of failover.sql

Max mirroring DB on a 64-bit sysstem?

According to BOL we know

"On a 32-bit system, database mirroring can support a maximum of about 10 databases per server instance because of the numbers of worker threads that are consumed by each database mirroring session."

My question is: What is maximum number of mirrored DB we can deploy on 64-bit system per one sql instance?

It depends. Do you have a 64-CPU box with 1 TB of RAM or a 4 CPU box with 4 GB? The variety of 64-bit hardware available makes specific guidance difficult.

You will need to test your configuration appropriately regardless.

|||

Peter thanks for you answer.

We have got the next configuration :

HP Superdome (1 cell) 4 CPU?(Dual core Itanium 2 1.6GHz, 24 MB Cache),?32GB.

|||

In the case of multiple databases, I use a different tack to overcome the problem. If I find any database failed over, I run SQL commands to fail them all over. "ALTER DATABASE [dbname] SET PARTNER FAILOVER" you must proceed the command with "USE [master]". It works in my case as i am running web code against multiple databases at any given point in time, so I have to have them all failover at the same time anyways. The statement to return the state of each database is "SELECT * from sys.database_mirroring WHERE mirroring_guid IS NOT NULL" I read the values programatically and run the appropriate failover statements depending on the values returned.

|||This was extremely useful, I copied it verbatim into a scheduled task that runs every minute and checks this, because we've had the same issue where only some but not all databases fail over. There should be an SQL Server feature to make multiple databases "atomic" for the purpose of failover.

Max mirroring DB on a 64-bit sysstem?

According to BOL we know

"On a 32-bit system, database mirroring can support a maximum of about 10 databases per server instance because of the numbers of worker threads that are consumed by each database mirroring session."

My question is: What is maximum number of mirrored DB we can deploy on 64-bit system per one sql instance?

It depends. Do you have a 64-CPU box with 1 TB of RAM or a 4 CPU box with 4 GB? The variety of 64-bit hardware available makes specific guidance difficult.

You will need to test your configuration appropriately regardless.

|||

Peter thanks for you answer.

We have got the next configuration :

HP Superdome (1 cell) 4 CPU?(Dual core Itanium 2 1.6GHz, 24 MB Cache),?32GB.

|||

In the case of multiple databases, I use a different tack to overcome the problem. If I find any database failed over, I run SQL commands to fail them all over. "ALTER DATABASE [dbname] SET PARTNER FAILOVER" you must proceed the command with "USE [master]". It works in my case as i am running web code against multiple databases at any given point in time, so I have to have them all failover at the same time anyways. The statement to return the state of each database is "SELECT * from sys.database_mirroring WHERE mirroring_guid IS NOT NULL" I read the values programatically and run the appropriate failover statements depending on the values returned.

|||This was extremely useful, I copied it verbatim into a scheduled task that runs every minute and checks this, because we've had the same issue where only some but not all databases fail over. There should be an SQL Server feature to make multiple databases "atomic" for the purpose of failover.

Max Memory Support of SQL 2000 Enterprise on Windows 2003 Enterpri

Pretty simple question, what is the maximum amount of memory SQL 2000
Enterprise Edition can support on Windows 2003 Enterprise Edition (all
refering to the 32-bit versions). Thanks!
32GB on Win 2003 Enterprise
64GB on Win 2003 Datacenter
(I think.)
*mike hodgson*
http://sqlnerd.blogspot.com
Marks70 wrote:

>Pretty simple question, what is the maximum amount of memory SQL 2000
>Enterprise Edition can support on Windows 2003 Enterprise Edition (all
>refering to the 32-bit versions). Thanks!
>
|||The maximum amount of memory that can be supported on Windows Server 2003 is
4 GB.
Refer => http://support.microsoft.com/?id=274750
Thanks,
Sree
"Marks70" wrote:

> Pretty simple question, what is the maximum amount of memory SQL 2000
> Enterprise Edition can support on Windows 2003 Enterprise Edition (all
> refering to the 32-bit versions). Thanks!
|||Yes but the question was about Windows 2003 Enterprise which is 32GB in the
same article.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:3DB7B61C-D8DF-4846-8A68-596D683CA237@.microsoft.com...[vbcol=seagreen]
> The maximum amount of memory that can be supported on Windows Server 2003
> is
> 4 GB.
> Refer => http://support.microsoft.com/?id=274750
> Thanks,
> Sree
>
> "Marks70" wrote:
|||Thanks guys!
"Marks70" wrote:

> Pretty simple question, what is the maximum amount of memory SQL 2000
> Enterprise Edition can support on Windows 2003 Enterprise Edition (all
> refering to the 32-bit versions). Thanks!

Max Memory Support of SQL 2000 Enterprise on Windows 2003 Enterpri

Pretty simple question, what is the maximum amount of memory SQL 2000
Enterprise Edition can support on Windows 2003 Enterprise Edition (all
refering to the 32-bit versions). Thanks!This is a multi-part message in MIME format.
--090006090404030906000503
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
32GB on Win 2003 Enterprise
64GB on Win 2003 Datacenter
(I think.)
--
*mike hodgson*
http://sqlnerd.blogspot.com
Marks70 wrote:
>Pretty simple question, what is the maximum amount of memory SQL 2000
>Enterprise Edition can support on Windows 2003 Enterprise Edition (all
>refering to the 32-bit versions). Thanks!
>
--090006090404030906000503
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>32GB on Win 2003 Enterprise<br>
64GB on Win 2003 Datacenter<br>
<br>
(I think.)<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font></span> <b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"><br>
<font face="Tahoma" size="2"><a href="http://links.10026.com/?link=http://sqlnerd.blogspot.com</a></font></span>">http://sqlnerd.blogspot.com">http://sqlnerd.blogspot.com</a></font></span>
</p>
</div>
<br>
<br>
Marks70 wrote:
<blockquote cite="mid91F52420-72D3-4203-BE73-5C9A3AD9783A@.microsoft.com"
type="cite">
<pre wrap="">Pretty simple question, what is the maximum amount of memory SQL 2000
Enterprise Edition can support on Windows 2003 Enterprise Edition (all
refering to the 32-bit versions). Thanks!
</pre>
</blockquote>
</body>
</html>
--090006090404030906000503--|||The maximum amount of memory that can be supported on Windows Server 2003 is
4 GB.
Refer => http://support.microsoft.com/?id=274750
Thanks,
Sree
"Marks70" wrote:
> Pretty simple question, what is the maximum amount of memory SQL 2000
> Enterprise Edition can support on Windows 2003 Enterprise Edition (all
> refering to the 32-bit versions). Thanks!|||Yes but the question was about Windows 2003 Enterprise which is 32GB in the
same article.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:3DB7B61C-D8DF-4846-8A68-596D683CA237@.microsoft.com...
> The maximum amount of memory that can be supported on Windows Server 2003
> is
> 4 GB.
> Refer => http://support.microsoft.com/?id=274750
> Thanks,
> Sree
>
> "Marks70" wrote:
>> Pretty simple question, what is the maximum amount of memory SQL 2000
>> Enterprise Edition can support on Windows 2003 Enterprise Edition (all
>> refering to the 32-bit versions). Thanks!|||Correction :) =>
The maximum amount of memory that can be supported on Windows Server 2003
is 4 GB. However, Windows Server 2003 Enterprise Edition supports 32 GB of
physical RAM.
Thanks,
Sree
"Sreejith G" wrote:
> The maximum amount of memory that can be supported on Windows Server 2003 is
> 4 GB.
> Refer => http://support.microsoft.com/?id=274750
> Thanks,
> Sree
>
> "Marks70" wrote:
> > Pretty simple question, what is the maximum amount of memory SQL 2000
> > Enterprise Edition can support on Windows 2003 Enterprise Edition (all
> > refering to the 32-bit versions). Thanks!|||Thanks guys!
"Marks70" wrote:
> Pretty simple question, what is the maximum amount of memory SQL 2000
> Enterprise Edition can support on Windows 2003 Enterprise Edition (all
> refering to the 32-bit versions). Thanks!sql

Max Memory Support of SQL 2000 Enterprise on Windows 2003 Enterpri

Pretty simple question, what is the maximum amount of memory SQL 2000
Enterprise Edition can support on Windows 2003 Enterprise Edition (all
refering to the 32-bit versions). Thanks!32GB on Win 2003 Enterprise
64GB on Win 2003 Datacenter
(I think.)
*mike hodgson*
http://sqlnerd.blogspot.com
Marks70 wrote:

>Pretty simple question, what is the maximum amount of memory SQL 2000
>Enterprise Edition can support on Windows 2003 Enterprise Edition (all
>refering to the 32-bit versions). Thanks!
>|||The maximum amount of memory that can be supported on Windows Server 2003 is
4 GB.
Refer => http://support.microsoft.com/?id=274750
Thanks,
Sree
"Marks70" wrote:

> Pretty simple question, what is the maximum amount of memory SQL 2000
> Enterprise Edition can support on Windows 2003 Enterprise Edition (all
> refering to the 32-bit versions). Thanks!|||Yes but the question was about Windows 2003 Enterprise which is 32GB in the
same article.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Sreejith G" <SreejithG@.discussions.microsoft.com> wrote in message
news:3DB7B61C-D8DF-4846-8A68-596D683CA237@.microsoft.com...[vbcol=seagreen]
> The maximum amount of memory that can be supported on Windows Server 2003
> is
> 4 GB.
> Refer => http://support.microsoft.com/?id=274750
> Thanks,
> Sree
>
> "Marks70" wrote:
>|||Thanks guys!
"Marks70" wrote:

> Pretty simple question, what is the maximum amount of memory SQL 2000
> Enterprise Edition can support on Windows 2003 Enterprise Edition (all
> refering to the 32-bit versions). Thanks!

Max memory for SSIS

If we have a SQL Server 2005 standard edition/Windows 2003 Standard Environment on a 32 bit 2 dual core proc Dell 2850 server, what is the maximum size of the memory we could possibly have?

Thank you,

Shiva

SQL 2005 standard doesn't have a maximum memory, you are constrained by your OS and hardware. I think it's around 4 gigs for 2003 standard 32bit.|||

yosonu wrote:

If we have a SQL Server 2005 standard edition/Windows 2003 Standard Environment on a 32 bit 2 dual core proc Dell 2850 server, what is the maximum size of the memory we could possibly have?

Thank you,

Shiva

Is this a question about SSIS? If so, read this: http://blogs.conchango.com/jamiethomson/archive/2005/05/29/1486.aspx

If not, try a different forum.

-Jamie

|||

The 32bit Windows limit is 2GB per process. You can increase this to 3GB, using the boot.ini switch, /3GB.

A classic tip around this is to use several packages and Execute Process Tasks to combine them, but set the out of process option on, as this means each package then gets 2GB as each is it's own process. For small packages this may be detrimental though.

sql

max memory

Hi All,
I noticed that SQL 2000 seems to be eating up a bit more memory
(about 100Mb more) than the maximum memory that I have set. Is this a
normal behavior?
Thanks.
Aramid
The MAX Memory setting is for the memory pool only and does not take into
account the MemToLeave area. The MemToLeave can take up to 384MB's in
addition to the Max Memory if there is enough to go around.
Andrew J. Kelly SQL MVP
"Aramid" <aramid@.hotmail.com> wrote in message
news:44kst11d8pu4g6nhmch70q9la3ngu02jav@.4ax.com...
> Hi All,
> I noticed that SQL 2000 seems to be eating up a bit more memory
> (about 100Mb more) than the maximum memory that I have set. Is this a
> normal behavior?
> Thanks.
> Aramid

max memory

Hi All,
I noticed that SQL 2000 seems to be eating up a bit more memory
(about 100Mb more) than the maximum memory that I have set. Is this a
normal behavior?
Thanks.
AramidThe MAX Memory setting is for the memory pool only and does not take into
account the MemToLeave area. The MemToLeave can take up to 384MB's in
addition to the Max Memory if there is enough to go around.
Andrew J. Kelly SQL MVP
"Aramid" <aramid@.hotmail.com> wrote in message
news:44kst11d8pu4g6nhmch70q9la3ngu02jav@.
4ax.com...
> Hi All,
> I noticed that SQL 2000 seems to be eating up a bit more memory
> (about 100Mb more) than the maximum memory that I have set. Is this a
> normal behavior?
> Thanks.
> Aramid

max memory

Hi All,
I noticed that SQL 2000 seems to be eating up a bit more memory
(about 100Mb more) than the maximum memory that I have set. Is this a
normal behavior?
Thanks.
AramidThe MAX Memory setting is for the memory pool only and does not take into
account the MemToLeave area. The MemToLeave can take up to 384MB's in
addition to the Max Memory if there is enough to go around.
--
Andrew J. Kelly SQL MVP
"Aramid" <aramid@.hotmail.com> wrote in message
news:44kst11d8pu4g6nhmch70q9la3ngu02jav@.4ax.com...
> Hi All,
> I noticed that SQL 2000 seems to be eating up a bit more memory
> (about 100Mb more) than the maximum memory that I have set. Is this a
> normal behavior?
> Thanks.
> Aramid

Max Length of a SQL User ID

Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
Thanks
Hello,
SQL Server login's maximum size is 128 characters. You can determine it's
size by examine sysxlogins table in master database. Look for "name"
attribute in sysxlogins table and check it's "size" property.
Regards,
Tomislav Kralj
"Sarah Kingswell" <skingswell@.xonitek.co.uk> wrote in message
news:%23rvzXCUKFHA.2648@.TK2MSFTNGP14.phx.gbl...
> Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
> Thanks
>
|||Sarah,
Are you talking about sysusers.uid? That is a smallint, so the max value
for that column would be 32767.
If you are talking about sysusers.name then the max length is 256, or
128 characters as its Unicode.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Sarah Kingswell wrote:
> Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
> Thanks
>

Max Length of a SQL User ID

Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
ThanksHello,
SQL Server login's maximum size is 128 characters. You can determine it's
size by examine sysxlogins table in master database. Look for "name"
attribute in sysxlogins table and check it's "size" property.
Regards,
Tomislav Kralj
"Sarah Kingswell" <skingswell@.xonitek.co.uk> wrote in message
news:%23rvzXCUKFHA.2648@.TK2MSFTNGP14.phx.gbl...
> Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
> Thanks
>|||Sarah,
Are you talking about sysusers.uid? That is a smallint, so the max value
for that column would be 32767.
If you are talking about sysusers.name then the max length is 256, or
128 characters as its Unicode.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Sarah Kingswell wrote:
> Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
> Thanks
>

Max Length of a SQL User ID

Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
ThanksHello,
SQL Server login's maximum size is 128 characters. You can determine it's
size by examine sysxlogins table in master database. Look for "name"
attribute in sysxlogins table and check it's "size" property.
Regards,
Tomislav Kralj
"Sarah Kingswell" <skingswell@.xonitek.co.uk> wrote in message
news:%23rvzXCUKFHA.2648@.TK2MSFTNGP14.phx.gbl...
> Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
> Thanks
>|||Sarah,
Are you talking about sysusers.uid? That is a smallint, so the max value
for that column would be 32767.
If you are talking about sysusers.name then the max length is 256, or
128 characters as its Unicode.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Sarah Kingswell wrote:
> Does anyone know the maximum length allowed for a SQL User ID in SQL 2000?
> Thanks
>

Max degree of recursion

Hi Everyone
As I understand it the maximum call stack level of recursive stored
procedures is 32. Is there at way around this limitation?
I want to make a procedure that traverses a tree structure in my database to
discover if a given node is above the input parameter. Ex:
CREATE TABLE Nodes
(
NodeID int,
ParentNodeID int
)
DECLARE @.MyNodeID int
DECLARE @.ParentNodeID int
DECLARE @.IsParent bit
SET @.MyNodeID = 42
SET @.ParentNodeID = 13
EXEC spIs_Parent @.MyNode, @.ParentNodeID, Is
... What is the best way to implement such a procedure?
Yours sincerely
Thomas Kejser
M.Sc, MCDBA
Do it the sloppy way without using recursion.
Do you have the code?
Tony Rogerson
SQL Server MVP
http://www.sqlserverfaq.com?mbr=21
(Create your own groups, Forum, FAQ's and a ton more)

Max degree of recursion

Hi Everyone
As I understand it the maximum call stack level of recursive stored
procedures is 32. Is there at way around this limitation?
I want to make a procedure that traverses a tree structure in my database to
discover if a given node is above the input parameter. Ex:
CREATE TABLE Nodes
(
NodeID int,
ParentNodeID int
)
DECLARE @.MyNodeID int
DECLARE @.ParentNodeID int
DECLARE @.IsParent bit
SET @.MyNodeID = 42
SET @.ParentNodeID = 13
EXEC spIs_Parent @.MyNode, @.ParentNodeID, Is
... What is the best way to implement such a procedure?
Yours sincerely
Thomas Kejser
M.Sc, MCDBADo it the sloppy way without using recursion.
Do you have the code?
Tony Rogerson
SQL Server MVP
http://www.sqlserverfaq.com?mbr=21
(Create your own groups, Forum, FAQ's and a ton more)

Max degree of recursion

Hi Everyone
As I understand it the maximum call stack level of recursive stored
procedures is 32. Is there at way around this limitation?
I want to make a procedure that traverses a tree structure in my database to
discover if a given node is above the input parameter. Ex:
CREATE TABLE Nodes
(
NodeID int,
ParentNodeID int
)
DECLARE @.MyNodeID int
DECLARE @.ParentNodeID int
DECLARE @.IsParent bit
SET @.MyNodeID = 42
SET @.ParentNodeID = 13
EXEC spIs_Parent @.MyNode, @.ParentNodeID, Is
... What is the best way to implement such a procedure?
--
Yours sincerely
Thomas Kejser
M.Sc, MCDBADo it the sloppy way without using recursion.
Do you have the code?
--
Tony Rogerson
SQL Server MVP
http://www.sqlserverfaq.com?mbr=21
(Create your own groups, Forum, FAQ's and a ton more)

Max Degree of Parallelism - clearification

Tracy you stated, "SQL itself will still use all of the processors, but one
query alone will use a maximum of 2 at one time." When the query runs I
understand it's limited to only utilizing 2 CPUs simultaneously, how do
threads play a role in this? Is it one thread per CPU? Or can multiple
threads run on a CPU?
"Tracy McKibben" <tracy@.realsqlguy.com> wrote in message
news:45782C05.8090107@.realsqlguy.com...
> Jaski wrote:
> Setting it to 2 will restrict any given query to using 2 processors
> simultaneously. SQL itself will still use all of the processors, but one
> query alone will use a maximum of 2 at one time.
>
> --
> Tracy McKibben
> MCDBA
> http://www.realsqlguy.com
On Thu, 07 Dec 2006 20:25:18 GMT, "Jaski" <Jaski@.nospam.com> wrote:

>Tracy you stated, "SQL itself will still use all of the processors, but one
>query alone will use a maximum of 2 at one time." When the query runs I
>understand it's limited to only utilizing 2 CPUs simultaneously, how do
>threads play a role in this? Is it one thread per CPU? Or can multiple
>threads run on a CPU?
Multiple threads can run on a CPU, that's for sure.
It is very confusing, but I think the MAXDOP SQL parameter may control
that, but not the number of physical processors. Or, not.
J.
|||On Fri, 8 Dec 2006 09:34:35 +0100, "Tibor Karaszi"
<tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote:

>A query executing in parallel will not use several threads on the same processor. That would
>decrease performance. SQL Server has one scheduler per processor (core, or logical if HT), and it
>will make sure that the query will use threads over different schedulers (i.e., processors).
I was commonly seeing seven and more SPIDs on a two-processor,
single-core, non-hyper'd system, SQL2K Enterprise.
So, SPID is not quite the same as thread, is it?
I was asking about this back in April and May:
[url]http://groups.google.com/group/microsoft.public.sqlserver.server/browse_thread/thread/d961ed7576f6a6f9/8336914737a3e20a?lnk=st&q=group%3Amicrosoft.public .sqlserver.*+author%3Ajxstern&rnum=16&hl=en#833691 4737a3e20a[/url]
J.
|||On Fri, 8 Dec 2006 21:20:36 +0100, "Tibor Karaszi"
<tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote:

>Hmm, I was pretty certain that SQL Server would not use several threads per SPID and processor
>(i.e., one spid would get maximum one thread per processor(=scheduler)). Did you see more rows then
>the number of processors (from sp_who or similar) with the same spid number?
Very definitely.
Certainly surprised me!!

>If so, then you can
>ignore my prior post (as I apparently then have misunderstood things).
OK.

>No. SQL Server has a thread pool. Also, SQL Server has a pool of SPIDs. Whenever a SPID need to do
>something, it uses one or more threads from the thread pool. I might be slightly off here with the
>details, so you might want to check out Slava Oks' blog for details.
http://blogs.msdn.com/slavao/
?
Looks good, thanks.
J.

Max Column Total in SQL Server 2005

Hello,

Is there a maximum total of columns that SQL Server 2005 limits? I have a rather lengthy import file in regards to column count, and was wondering if there was a total number of columns that a table is limited to.

Thanks.

I think it is 255, I am not so sure

|||

please check this, it may help you.

http://msdn2.microsoft.com/en-us/library/ms143432.aspx