Showing posts with label edition. Show all posts
Showing posts with label edition. Show all posts

Sunday, March 25, 2012

A couple of easy questions

Hi everyone,

Running Windows 2003 x64 and Sql25k 64-bit edition

We just have a couple of questions related with our system:

-What is Sql Server VSS Writer service for?

-What sort of implications must we assume when Integration Services service is running as NT AUTHORITY\NetworkService

Any link or advice would be welcomed.

Thanks for your time,

SQL Writer Service
(http://msdn2.microsoft.com/en-us/library/ms175536.aspx)

Setting Up Windows Service Accounts
(http://msdn2.microsoft.com/en-us/library/309b9dac-0b3a-4617-85ef-c4519ce9d014.aspx)

For SSIS the implications are much the same as any service, just bear in mind what the SSIS service does, not a lot really.

|||Thank you|||Be sure to mark the answers to your questions as an answer to the thread.

A connection was successfully established with the server, but then an error occurred during the

I have just installed MS SQL Server 2005 Express edition along with the SSMSE. I am using windows authentication. When I open SSMSE it connects me to a 'local instance' of the server. From there I right click on Database and select to add a new Database and I get the error above. I think I only need to allow local connections to the engine but I have tried allowing remote conections with all varations of named pipes and TCP/IP. I am running on Windows XP SP2 (home).Hi,

could you please post the whole error message ?

You might take a look at this site in the meantime: http://blogs.msdn.com/sql_protocols/Default.aspx?p=2

HTH; Jens K. Suessmeyer.

http://www.sqlserver2005.de

Monday, March 19, 2012

8GB RAM in SQL Server

Hi,
I'm just designing a server... What can I do with 8GB RAM in the Box?
Analysis Services is limited to 8GB. The Enterprise Edition of SQL Server
can use max.8GB RAM. Windows 2003 Enterprise Edition can use 8GB, too.
So I can use 3GB for Analysis Services and the remaining 5GB are used for
SQL Server and the OS? Is this right?
Thanks
ThomasActually, there is no direct answer for this. It depends
on how much memory the analysis server requires for cubes
and memory required for SQL Server.
It also depends on any other applications running on the
same box.
In General, You have to allocate for OS,SQLServer,analysis
Server and then for other applications.
Please read this to get some idea on how SQL Server memory
works. http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/adminsql/ad_config_9zfy.asp
Also , read "memory architecture" from BOL.
To allocate memory for Analysis Server, stop and start the
analysis services and open the task manager and look for
memory used by the processess "msmdsrv.exe"
and "msmdvldm.exe". The sum of these memory is minimum
required for analysis services to start.
SQLVarad (MCDBA-1999,MCSE-1999)
>--Original Message--
>Hi,
>I'm just designing a server... What can I do with 8GB RAM
in the Box?
>Analysis Services is limited to 8GB. The Enterprise
Edition of SQL Server
>can use max.8GB RAM. Windows 2003 Enterprise Edition can
use 8GB, too.
>So I can use 3GB for Analysis Services and the remaining
5GB are used for
>SQL Server and the OS? Is this right?
>
>Thanks
>
>Thomas
>
>.
>|||Hi,
thanks, that pointed me in the right direction...
Thomas
"SQLVarad" <SQLVarad@.hotmail.com> schrieb im Newsbeitrag
news:010c01c3a3d4$6cc8f790$a601280a@.phx.gbl...
> Actually, there is no direct answer for this. It depends
> on how much memory the analysis server requires for cubes
> and memory required for SQL Server.
> It also depends on any other applications running on the
> same box.
> In General, You have to allocate for OS,SQLServer,analysis
> Server and then for other applications.
> Please read this to get some idea on how SQL Server memory
> works. http://msdn.microsoft.com/library/default.asp?
> url=/library/en-us/adminsql/ad_config_9zfy.asp
> Also , read "memory architecture" from BOL.
> To allocate memory for Analysis Server, stop and start the
> analysis services and open the task manager and look for
> memory used by the processess "msmdsrv.exe"
> and "msmdvldm.exe". The sum of these memory is minimum
> required for analysis services to start.
> SQLVarad (MCDBA-1999,MCSE-1999)
>
> >--Original Message--
> >Hi,
> >
> >I'm just designing a server... What can I do with 8GB RAM
> in the Box?
> >Analysis Services is limited to 8GB. The Enterprise
> Edition of SQL Server
> >can use max.8GB RAM. Windows 2003 Enterprise Edition can
> use 8GB, too.
> >So I can use 3GB for Analysis Services and the remaining
> 5GB are used for
> >SQL Server and the OS? Is this right?
> >
> >
> >Thanks
> >
> >
> >Thomas
> >
> >
> >.
> >

Sunday, March 11, 2012

8000 char Row limit

is the 8000 char row limit only an issue in standard
edition? If I upgrade to enterprise edition will I not
have this problem? Thanks.
It has nothing to do with the edition; it is a storage / engine limitation.
What exactly are you trying to do? Are you aware of the reasons for the
limit?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Billy Dodson" <billy@.pmicromart.com> wrote in message
news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
> is the 8000 char row limit only an issue in standard
> edition? If I upgrade to enterprise edition will I not
> have this problem? Thanks.
|||The actual row limit is 8060, and the max char/varchar column size is 8000
bytes.
"Billy Dodson" <billy@.pmicromart.com> wrote in message
news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
> is the 8000 char row limit only an issue in standard
> edition? If I upgrade to enterprise edition will I not
> have this problem? Thanks.
|||This sql server is running our Microsoft CRM database. I
am trying to create some custom attributes. When I try to
create one it says that I am at the 8000 char row limit.
I can not delete any attributes. Is there not a way
around this? Thanks for your replys.

>--Original Message--
>It has nothing to do with the edition; it is a storage /
engine limitation.
>What exactly are you trying to do? Are you aware of the
reasons for the
>limit?
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>
>"Billy Dodson" <billy@.pmicromart.com> wrote in message
>news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
>
>.
>
|||Is there any way around the 8000 byte limit?

>--Original Message--
>The actual row limit is 8060, and the max char/varchar
column size is 8000
>bytes.
>"Billy Dodson" <billy@.pmicromart.com> wrote in message
>news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
>
>.
>
|||The error message is just a warning. You can go ahead and create a table
that is wider, just don't expect to use it all. For example:
CREATE TABLE dbo.blat
(
bar1 VARCHAR(5000),
bar2 VARCHAR(5000)
)
GO
Warning: The table 'blat' has been created but its maximum row size (10025)
exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a
row in this table will fail if the resulting row length exceeds 8060 bytes.
As the message states, the table was still created. However, populating it
with data will be more challenging. These work fine:
INSERT blat SELECT 'a', 'b'
INSERT blat SELECT REPLICATE('a', 5000), 'b'
INSERT blat SELECT 'a', REPLICATE('b', 5000)
But when you try and send more than 8060 bytes, you will have problems, e.g.
INSERT blat SELECT
REPLICATE('a', 5000), REPLICATE('b', 5000)
You get:
Server: Msg 511, Level 16, State 1, Line 1
Cannot create a row of size 10013 which is greater than the allowable
maximum of 8060.
The statement has been terminated.
What I recommend is storing any larger attributes in a separate table and
use relationships for data integrity.
Maybe you can show the code that represents "when I try to create one" and
the ACTUAL error message you receive, not your casual interpretation...
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189ae01c420b2$c7d24410$a601280a@.phx.gbl...
> This sql server is running our Microsoft CRM database. I
> am trying to create some custom attributes. When I try to
> create one it says that I am at the 8000 char row limit.
> I can not delete any attributes. Is there not a way
> around this? Thanks for your replys.
|||I am not trying to manually create this table. The table
is created upon the installation of CRM and I am trying to
add an attribute to it within microsoft CRM. In CRM i get
the following error:
An error occurred during the addition of the new field.
The addition failed. For more information, see the event
log.
Event log error:
1.
dmLog: Failed to add new Picklist attribute (CFPcatagory)
to Account entity.
2.
dmLog: New size of the attribute ({53B8A5DA-324C-4926-9F57-
B21C02C1E8C7}) exceeds the SQL Server row limit of 8000
bytes.
I dont know if you are familiar with CRM deployment
manager, there is a section to create mappings, which
might be the same as the relationships as your talking
about. It will not let me modify any existing attribute,
even the ones that I have created. I cant delete an
attribute either.
Thanks again for your help.

>--Original Message--
>The error message is just a warning. You can go ahead
and create a table
>that is wider, just don't expect to use it all. For
example:
>CREATE TABLE dbo.blat
>(
> bar1 VARCHAR(5000),
> bar2 VARCHAR(5000)
>)
>GO
>Warning: The table 'blat' has been created but its
maximum row size (10025)
>exceeds the maximum number of bytes per row (8060).
INSERT or UPDATE of a
>row in this table will fail if the resulting row length
exceeds 8060 bytes.
>As the message states, the table was still created.
However, populating it
>with data will be more challenging. These work fine:
>INSERT blat SELECT 'a', 'b'
>INSERT blat SELECT REPLICATE('a', 5000), 'b'
>INSERT blat SELECT 'a', REPLICATE('b', 5000)
>But when you try and send more than 8060 bytes, you will
have problems, e.g.
>INSERT blat SELECT
> REPLICATE('a', 5000), REPLICATE('b', 5000)
>You get:
>Server: Msg 511, Level 16, State 1, Line 1
>Cannot create a row of size 10013 which is greater than
the allowable
>maximum of 8060.
>The statement has been terminated.
>What I recommend is storing any larger attributes in a
separate table and
>use relationships for data integrity.
>Maybe you can show the code that represents "when I try
to create one" and
>the ACTUAL error message you receive, not your casual
interpretation...
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>
>"billy dodson" <billy@.pmicromart.com> wrote in message
>news:189ae01c420b2$c7d24410$a601280a@.phx.gbl...
I
to
>
>.
>
|||This limitation will be removed in Yukon. You will be able to do the
following (for example):
create table t1 (c1 varchar (5000), c2 varchar (5000))
go
insert into t1 values (replicate ('a', 5000), replicate ('b', 5000))
go
with no problems.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189af01c420b2$e74a99f0$a601280a@.phx.gbl...
> Is there any way around the 8000 byte limit?
> column size is 8000
|||Billy,
As stated, it is only a warning. How much of the 8060 char limit is being
used by the unmodified table?
If you have 16 bytes left, you can assign the new attribute to a text or
ntext column, and that will fit. Of course, you then have to deal with the
issues that arise from using text columns.
You can create an attribute table of nothing more than an identity or guid
column and the attribute and then just store the identity (4 bytes) or
rowguid (16 bytes) in your table.
You might also run statistics on the actual size of data being stored vs the
field size for all fields in the table. Knowing this will give you an idea
of how much space you can "safely" assign to the new attribute. The caveat
here is that you will have to check the length of everything on inserts and
updates.
Regards,
John
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189af01c420b2$e74a99f0$a601280a@.phx.gbl...[color=darkblue]
> Is there any way around the 8000 byte limit?
> column size is 8000
|||sounds like one for the CRM group if there is one - being unable to remove
user-defined attributes sounds like a design flaw
Niall Litchfield
Oracle DBA
Audit Commission UK
http://www.niall.litchfield.dial.pipex.com/
<anonymous@.discussions.microsoft.com> wrote in message
news:1bad601c420b8$297548c0$a101280a@.phx.gbl...[vbcol=seagreen]
> I am not trying to manually create this table. The table
> is created upon the installation of CRM and I am trying to
> add an attribute to it within microsoft CRM. In CRM i get
> the following error:
> An error occurred during the addition of the new field.
> The addition failed. For more information, see the event
> log.
> Event log error:
> 1.
> dmLog: Failed to add new Picklist attribute (CFPcatagory)
> to Account entity.
> 2.
> dmLog: New size of the attribute ({53B8A5DA-324C-4926-9F57-
> B21C02C1E8C7}) exceeds the SQL Server row limit of 8000
> bytes.
>
> I dont know if you are familiar with CRM deployment
> manager, there is a section to create mappings, which
> might be the same as the relationships as your talking
> about. It will not let me modify any existing attribute,
> even the ones that I have created. I cant delete an
> attribute either.
> Thanks again for your help.
>
> and create a table
> example:
> maximum row size (10025)
> INSERT or UPDATE of a
> exceeds 8060 bytes.
> However, populating it
> have problems, e.g.
> the allowable
> separate table and
> to create one" and
> interpretation...
> I
> to

8000 char Row limit

is the 8000 char row limit only an issue in standard
edition? If I upgrade to enterprise edition will I not
have this problem? Thanks.It has nothing to do with the edition; it is a storage / engine limitation.
What exactly are you trying to do? Are you aware of the reasons for the
limit?
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Billy Dodson" <billy@.pmicromart.com> wrote in message
news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
> is the 8000 char row limit only an issue in standard
> edition? If I upgrade to enterprise edition will I not
> have this problem? Thanks.|||The actual row limit is 8060, and the max char/varchar column size is 8000
bytes.
"Billy Dodson" <billy@.pmicromart.com> wrote in message
news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
> is the 8000 char row limit only an issue in standard
> edition? If I upgrade to enterprise edition will I not
> have this problem? Thanks.|||This sql server is running our Microsoft CRM database. I
am trying to create some custom attributes. When I try to
create one it says that I am at the 8000 char row limit.
I can not delete any attributes. Is there not a way
around this? Thanks for your replys.
>--Original Message--
>It has nothing to do with the edition; it is a storage /
engine limitation.
>What exactly are you trying to do? Are you aware of the
reasons for the
>limit?
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>
>"Billy Dodson" <billy@.pmicromart.com> wrote in message
>news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
>> is the 8000 char row limit only an issue in standard
>> edition? If I upgrade to enterprise edition will I not
>> have this problem? Thanks.
>
>.
>|||Is there any way around the 8000 byte limit?
>--Original Message--
>The actual row limit is 8060, and the max char/varchar
column size is 8000
>bytes.
>"Billy Dodson" <billy@.pmicromart.com> wrote in message
>news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
>> is the 8000 char row limit only an issue in standard
>> edition? If I upgrade to enterprise edition will I not
>> have this problem? Thanks.
>
>.
>|||The error message is just a warning. You can go ahead and create a table
that is wider, just don't expect to use it all. For example:
CREATE TABLE dbo.blat
(
bar1 VARCHAR(5000),
bar2 VARCHAR(5000)
)
GO
Warning: The table 'blat' has been created but its maximum row size (10025)
exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a
row in this table will fail if the resulting row length exceeds 8060 bytes.
As the message states, the table was still created. However, populating it
with data will be more challenging. These work fine:
INSERT blat SELECT 'a', 'b'
INSERT blat SELECT REPLICATE('a', 5000), 'b'
INSERT blat SELECT 'a', REPLICATE('b', 5000)
But when you try and send more than 8060 bytes, you will have problems, e.g.
INSERT blat SELECT
REPLICATE('a', 5000), REPLICATE('b', 5000)
You get:
Server: Msg 511, Level 16, State 1, Line 1
Cannot create a row of size 10013 which is greater than the allowable
maximum of 8060.
The statement has been terminated.
What I recommend is storing any larger attributes in a separate table and
use relationships for data integrity.
Maybe you can show the code that represents "when I try to create one" and
the ACTUAL error message you receive, not your casual interpretation...
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189ae01c420b2$c7d24410$a601280a@.phx.gbl...
> This sql server is running our Microsoft CRM database. I
> am trying to create some custom attributes. When I try to
> create one it says that I am at the 8000 char row limit.
> I can not delete any attributes. Is there not a way
> around this? Thanks for your replys.|||I am not trying to manually create this table. The table
is created upon the installation of CRM and I am trying to
add an attribute to it within microsoft CRM. In CRM i get
the following error:
An error occurred during the addition of the new field.
The addition failed. For more information, see the event
log.
Event log error:
1.
dmLog: Failed to add new Picklist attribute (CFPcatagory)
to Account entity.
2.
dmLog: New size of the attribute ({53B8A5DA-324C-4926-9F57-
B21C02C1E8C7}) exceeds the SQL Server row limit of 8000
bytes.
I dont know if you are familiar with CRM deployment
manager, there is a section to create mappings, which
might be the same as the relationships as your talking
about. It will not let me modify any existing attribute,
even the ones that I have created. I cant delete an
attribute either.
Thanks again for your help.
>--Original Message--
>The error message is just a warning. You can go ahead
and create a table
>that is wider, just don't expect to use it all. For
example:
>CREATE TABLE dbo.blat
>(
> bar1 VARCHAR(5000),
> bar2 VARCHAR(5000)
>)
>GO
>Warning: The table 'blat' has been created but its
maximum row size (10025)
>exceeds the maximum number of bytes per row (8060).
INSERT or UPDATE of a
>row in this table will fail if the resulting row length
exceeds 8060 bytes.
>As the message states, the table was still created.
However, populating it
>with data will be more challenging. These work fine:
>INSERT blat SELECT 'a', 'b'
>INSERT blat SELECT REPLICATE('a', 5000), 'b'
>INSERT blat SELECT 'a', REPLICATE('b', 5000)
>But when you try and send more than 8060 bytes, you will
have problems, e.g.
>INSERT blat SELECT
> REPLICATE('a', 5000), REPLICATE('b', 5000)
>You get:
>Server: Msg 511, Level 16, State 1, Line 1
>Cannot create a row of size 10013 which is greater than
the allowable
>maximum of 8060.
>The statement has been terminated.
>What I recommend is storing any larger attributes in a
separate table and
>use relationships for data integrity.
>Maybe you can show the code that represents "when I try
to create one" and
>the ACTUAL error message you receive, not your casual
interpretation...
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>
>"billy dodson" <billy@.pmicromart.com> wrote in message
>news:189ae01c420b2$c7d24410$a601280a@.phx.gbl...
>> This sql server is running our Microsoft CRM database.
I
>> am trying to create some custom attributes. When I try
to
>> create one it says that I am at the 8000 char row limit.
>> I can not delete any attributes. Is there not a way
>> around this? Thanks for your replys.
>
>.
>|||This limitation will be removed in Yukon. You will be able to do the
following (for example):
create table t1 (c1 varchar (5000), c2 varchar (5000))
go
insert into t1 values (replicate ('a', 5000), replicate ('b', 5000))
go
with no problems.
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189af01c420b2$e74a99f0$a601280a@.phx.gbl...
> Is there any way around the 8000 byte limit?
> >--Original Message--
> >The actual row limit is 8060, and the max char/varchar
> column size is 8000
> >bytes.
> >"Billy Dodson" <billy@.pmicromart.com> wrote in message
> >news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
> >> is the 8000 char row limit only an issue in standard
> >> edition? If I upgrade to enterprise edition will I not
> >> have this problem? Thanks.
> >
> >
> >.
> >|||Billy,
As stated, it is only a warning. How much of the 8060 char limit is being
used by the unmodified table?
If you have 16 bytes left, you can assign the new attribute to a text or
ntext column, and that will fit. Of course, you then have to deal with the
issues that arise from using text columns.
You can create an attribute table of nothing more than an identity or guid
column and the attribute and then just store the identity (4 bytes) or
rowguid (16 bytes) in your table.
You might also run statistics on the actual size of data being stored vs the
field size for all fields in the table. Knowing this will give you an idea
of how much space you can "safely" assign to the new attribute. The caveat
here is that you will have to check the length of everything on inserts and
updates.
Regards,
John
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189af01c420b2$e74a99f0$a601280a@.phx.gbl...
> Is there any way around the 8000 byte limit?
> >--Original Message--
> >The actual row limit is 8060, and the max char/varchar
> column size is 8000
> >bytes.
> >"Billy Dodson" <billy@.pmicromart.com> wrote in message
> >news:1b64b01c420a7$4331a210$a301280a@.phx.gbl...
> >> is the 8000 char row limit only an issue in standard
> >> edition? If I upgrade to enterprise edition will I not
> >> have this problem? Thanks.
> >
> >
> >.
> >|||sounds like one for the CRM group if there is one - being unable to remove
user-defined attributes sounds like a design flaw
--
Niall Litchfield
Oracle DBA
Audit Commission UK
http://www.niall.litchfield.dial.pipex.com/
<anonymous@.discussions.microsoft.com> wrote in message
news:1bad601c420b8$297548c0$a101280a@.phx.gbl...
> I am not trying to manually create this table. The table
> is created upon the installation of CRM and I am trying to
> add an attribute to it within microsoft CRM. In CRM i get
> the following error:
> An error occurred during the addition of the new field.
> The addition failed. For more information, see the event
> log.
> Event log error:
> 1.
> dmLog: Failed to add new Picklist attribute (CFPcatagory)
> to Account entity.
> 2.
> dmLog: New size of the attribute ({53B8A5DA-324C-4926-9F57-
> B21C02C1E8C7}) exceeds the SQL Server row limit of 8000
> bytes.
>
> I dont know if you are familiar with CRM deployment
> manager, there is a section to create mappings, which
> might be the same as the relationships as your talking
> about. It will not let me modify any existing attribute,
> even the ones that I have created. I cant delete an
> attribute either.
> Thanks again for your help.
>
> >--Original Message--
> >The error message is just a warning. You can go ahead
> and create a table
> >that is wider, just don't expect to use it all. For
> example:
> >
> >CREATE TABLE dbo.blat
> >(
> > bar1 VARCHAR(5000),
> > bar2 VARCHAR(5000)
> >)
> >GO
> >
> >Warning: The table 'blat' has been created but its
> maximum row size (10025)
> >exceeds the maximum number of bytes per row (8060).
> INSERT or UPDATE of a
> >row in this table will fail if the resulting row length
> exceeds 8060 bytes.
> >
> >As the message states, the table was still created.
> However, populating it
> >with data will be more challenging. These work fine:
> >
> >INSERT blat SELECT 'a', 'b'
> >INSERT blat SELECT REPLICATE('a', 5000), 'b'
> >INSERT blat SELECT 'a', REPLICATE('b', 5000)
> >
> >But when you try and send more than 8060 bytes, you will
> have problems, e.g.
> >
> >INSERT blat SELECT
> > REPLICATE('a', 5000), REPLICATE('b', 5000)
> >
> >You get:
> >
> >Server: Msg 511, Level 16, State 1, Line 1
> >Cannot create a row of size 10013 which is greater than
> the allowable
> >maximum of 8060.
> >The statement has been terminated.
> >
> >What I recommend is storing any larger attributes in a
> separate table and
> >use relationships for data integrity.
> >
> >Maybe you can show the code that represents "when I try
> to create one" and
> >the ACTUAL error message you receive, not your casual
> interpretation...
> >
> >--
> >Aaron Bertrand
> >SQL Server MVP
> >http://www.aspfaq.com/
> >
> >
> >
> >
> >"billy dodson" <billy@.pmicromart.com> wrote in message
> >news:189ae01c420b2$c7d24410$a601280a@.phx.gbl...
> >> This sql server is running our Microsoft CRM database.
> I
> >> am trying to create some custom attributes. When I try
> to
> >> create one it says that I am at the 8000 char row limit.
> >> I can not delete any attributes. Is there not a way
> >> around this? Thanks for your replys.
> >
> >
> >.
> >

8000 char Row limit

is the 8000 char row limit only an issue in standard
edition? If I upgrade to enterprise edition will I not
have this problem? Thanks.It has nothing to do with the edition; it is a storage / engine limitation.
What exactly are you trying to do? Are you aware of the reasons for the
limit?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"Billy Dodson" <billy@.pmicromart.com> wrote in message
news:1b64b01c420a7$4331a210$a301280a@.phx
.gbl...
> is the 8000 char row limit only an issue in standard
> edition? If I upgrade to enterprise edition will I not
> have this problem? Thanks.|||The actual row limit is 8060, and the max char/varchar column size is 8000
bytes.
"Billy Dodson" <billy@.pmicromart.com> wrote in message
news:1b64b01c420a7$4331a210$a301280a@.phx
.gbl...
> is the 8000 char row limit only an issue in standard
> edition? If I upgrade to enterprise edition will I not
> have this problem? Thanks.|||This sql server is running our Microsoft CRM database. I
am trying to create some custom attributes. When I try to
create one it says that I am at the 8000 char row limit.
I can not delete any attributes. Is there not a way
around this? Thanks for your replys.

>--Original Message--
>It has nothing to do with the edition; it is a storage /
engine limitation.
>What exactly are you trying to do? Are you aware of the
reasons for the
>limit?
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>
>"Billy Dodson" <billy@.pmicromart.com> wrote in message
> news:1b64b01c420a7$4331a210$a301280a@.phx
.gbl...
>
>.
>|||Is there any way around the 8000 byte limit?

>--Original Message--
>The actual row limit is 8060, and the max char/varchar
column size is 8000
>bytes.
>"Billy Dodson" <billy@.pmicromart.com> wrote in message
> news:1b64b01c420a7$4331a210$a301280a@.phx
.gbl...
>
>.
>|||The error message is just a warning. You can go ahead and create a table
that is wider, just don't expect to use it all. For example:
CREATE TABLE dbo.blat
(
bar1 VARCHAR(5000),
bar2 VARCHAR(5000)
)
GO
Warning: The table 'blat' has been created but its maximum row size (10025)
exceeds the maximum number of bytes per row (8060). INSERT or UPDATE of a
row in this table will fail if the resulting row length exceeds 8060 bytes.
As the message states, the table was still created. However, populating it
with data will be more challenging. These work fine:
INSERT blat SELECT 'a', 'b'
INSERT blat SELECT REPLICATE('a', 5000), 'b'
INSERT blat SELECT 'a', REPLICATE('b', 5000)
But when you try and send more than 8060 bytes, you will have problems, e.g.
INSERT blat SELECT
REPLICATE('a', 5000), REPLICATE('b', 5000)
You get:
Server: Msg 511, Level 16, State 1, Line 1
Cannot create a row of size 10013 which is greater than the allowable
maximum of 8060.
The statement has been terminated.
What I recommend is storing any larger attributes in a separate table and
use relationships for data integrity.
Maybe you can show the code that represents "when I try to create one" and
the ACTUAL error message you receive, not your casual interpretation...
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189ae01c420b2$c7d24410$a601280a@.phx
.gbl...
> This sql server is running our Microsoft CRM database. I
> am trying to create some custom attributes. When I try to
> create one it says that I am at the 8000 char row limit.
> I can not delete any attributes. Is there not a way
> around this? Thanks for your replys.|||I am not trying to manually create this table. The table
is created upon the installation of CRM and I am trying to
add an attribute to it within microsoft CRM. In CRM i get
the following error:
An error occurred during the addition of the new field.
The addition failed. For more information, see the event
log.
Event log error:
1.
dmLog: Failed to add new Picklist attribute (CFPcatagory)
to Account entity.
2.
dmLog: New size of the attribute ({53B8A5DA-324C-4926-9F57-
B21C02C1E8C7}) exceeds the SQL Server row limit of 8000
bytes.
I dont know if you are familiar with CRM deployment
manager, there is a section to create mappings, which
might be the same as the relationships as your talking
about. It will not let me modify any existing attribute,
even the ones that I have created. I cant delete an
attribute either.
Thanks again for your help.

>--Original Message--
>The error message is just a warning. You can go ahead
and create a table
>that is wider, just don't expect to use it all. For
example:
>CREATE TABLE dbo.blat
>(
> bar1 VARCHAR(5000),
> bar2 VARCHAR(5000)
> )
>GO
>Warning: The table 'blat' has been created but its
maximum row size (10025)
>exceeds the maximum number of bytes per row (8060).
INSERT or UPDATE of a
>row in this table will fail if the resulting row length
exceeds 8060 bytes.
>As the message states, the table was still created.
However, populating it
>with data will be more challenging. These work fine:
>INSERT blat SELECT 'a', 'b'
>INSERT blat SELECT REPLICATE('a', 5000), 'b'
>INSERT blat SELECT 'a', REPLICATE('b', 5000)
>But when you try and send more than 8060 bytes, you will
have problems, e.g.
>INSERT blat SELECT
> REPLICATE('a', 5000), REPLICATE('b', 5000)
>You get:
>Server: Msg 511, Level 16, State 1, Line 1
>Cannot create a row of size 10013 which is greater than
the allowable
>maximum of 8060.
>The statement has been terminated.
>What I recommend is storing any larger attributes in a
separate table and
>use relationships for data integrity.
>Maybe you can show the code that represents "when I try
to create one" and
>the ACTUAL error message you receive, not your casual
interpretation...
>--
>Aaron Bertrand
>SQL Server MVP
>http://www.aspfaq.com/
>
>
>"billy dodson" <billy@.pmicromart.com> wrote in message
> news:189ae01c420b2$c7d24410$a601280a@.phx
.gbl...
I
to
>
>.
>|||This limitation will be removed in Yukon. You will be able to do the
following (for example):
create table t1 (c1 varchar (5000), c2 varchar (5000))
go
insert into t1 values (replicate ('a', 5000), replicate ('b', 5000))
go
with no problems.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189af01c420b2$e74a99f0$a601280a@.phx
.gbl...
> Is there any way around the 8000 byte limit?
>
> column size is 8000|||Billy,
As stated, it is only a warning. How much of the 8060 char limit is being
used by the unmodified table?
If you have 16 bytes left, you can assign the new attribute to a text or
ntext column, and that will fit. Of course, you then have to deal with the
issues that arise from using text columns.
You can create an attribute table of nothing more than an identity or guid
column and the attribute and then just store the identity (4 bytes) or
rowguid (16 bytes) in your table.
You might also run statistics on the actual size of data being stored vs the
field size for all fields in the table. Knowing this will give you an idea
of how much space you can "safely" assign to the new attribute. The caveat
here is that you will have to check the length of everything on inserts and
updates.
Regards,
John
"billy dodson" <billy@.pmicromart.com> wrote in message
news:189af01c420b2$e74a99f0$a601280a@.phx
.gbl...
> Is there any way around the 8000 byte limit?
>
> column size is 8000|||sounds like one for the CRM group if there is one - being unable to remove
user-defined attributes sounds like a design flaw
Niall Litchfield
Oracle DBA
Audit Commission UK
http://www.niall.litchfield.dial.pipex.com/
<anonymous@.discussions.microsoft.com> wrote in message
news:1bad601c420b8$297548c0$a101280a@.phx
.gbl...
> I am not trying to manually create this table. The table
> is created upon the installation of CRM and I am trying to
> add an attribute to it within microsoft CRM. In CRM i get
> the following error:
> An error occurred during the addition of the new field.
> The addition failed. For more information, see the event
> log.
> Event log error:
> 1.
> dmLog: Failed to add new Picklist attribute (CFPcatagory)
> to Account entity.
> 2.
> dmLog: New size of the attribute ({53B8A5DA-324C-4926-9F57-
> B21C02C1E8C7}) exceeds the SQL Server row limit of 8000
> bytes.
>
> I dont know if you are familiar with CRM deployment
> manager, there is a section to create mappings, which
> might be the same as the relationships as your talking
> about. It will not let me modify any existing attribute,
> even the ones that I have created. I cant delete an
> attribute either.
> Thanks again for your help.
>
> and create a table
> example:
> maximum row size (10025)
> INSERT or UPDATE of a
> exceeds 8060 bytes.
> However, populating it
> have problems, e.g.
> the allowable
> separate table and
> to create one" and
> interpretation...
> I
> to

8 GB of RAM installed

SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced Server. The server has 8 GB of RAM installed but for some reason SQL Server is only utilizing less than 4 GB. What would the likely cause be?
Three thoughts:
You are not using /3GB /PAE within the boot.ini
You have not configured SQL Server to with the "awe enabled" option (exec
sp_configure).
Memory usage is being restricted by min server memory (MB) and max server
memory (MB) (exec sp_configure).
Keith
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:A4DAD1E0-5C6A-49D4-8631-6DE54777B44B@.microsoft.com...
> SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced
Server. The server has 8 GB of RAM installed but for some reason SQL Server
is only utilizing less than 4 GB. What would the likely cause be?
|||Are you using the /3GB in your boot.ini? Look in books online under
"Managing AWE Memory."
-John Oakes
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:A4DAD1E0-5C6A-49D4-8631-6DE54777B44B@.microsoft.com...
> SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced
Server. The server has 8 GB of RAM installed but for some reason SQL Server
is only utilizing less than 4 GB. What would the likely cause be?
|||All those option is set. Still same problem
"John Oakes" wrote:

> Are you using the /3GB in your boot.ini? Look in books online under
> "Managing AWE Memory."
> -John Oakes
> "Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
> news:A4DAD1E0-5C6A-49D4-8631-6DE54777B44B@.microsoft.com...
> Server. The server has 8 GB of RAM installed but for some reason SQL Server
> is only utilizing less than 4 GB. What would the likely cause be?
>
>
|||Did you reboot after changing boot.ini?
-John Oakes
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:188FFB29-DDE5-42B3-A802-DC671FC7B68A@.microsoft.com...[vbcol=seagreen]
> All those option is set. Still same problem
> "John Oakes" wrote:
Advanced[vbcol=seagreen]
Server[vbcol=seagreen]
|||You also need the /PAE set in the Boot.ini.
Andrew J. Kelly SQL MVP
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:188FFB29-DDE5-42B3-A802-DC671FC7B68A@.microsoft.com...[vbcol=seagreen]
> All those option is set. Still same problem
> "John Oakes" wrote:
Advanced[vbcol=seagreen]
Server[vbcol=seagreen]
|||Serverdba wrote:

> SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced Server. The server has 8 GB of RAM installed but for some reason SQL Server is only utilizing less than 4 GB. What would the likely cause be?
Hi,
The Account which starts the SQL Service must have the privilege "lock
pages in memory" - you can set this in the local policy settings

8 GB of RAM installed

SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced Ser
ver. The server has 8 GB of RAM installed but for some reason SQL Server is
only utilizing less than 4 GB. What would the likely cause be?Three thoughts:
You are not using /3GB /PAE within the boot.ini
You have not configured SQL Server to with the "awe enabled" option (exec
sp_configure).
Memory usage is being restricted by min server memory (MB) and max server
memory (MB) (exec sp_configure).
Keith
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:A4DAD1E0-5C6A-49D4-8631-6DE54777B44B@.microsoft.com...
> SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced
Server. The server has 8 GB of RAM installed but for some reason SQL Server
is only utilizing less than 4 GB. What would the likely cause be?|||Are you using the /3GB in your boot.ini? Look in books online under
"Managing AWE Memory."
-John Oakes
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:A4DAD1E0-5C6A-49D4-8631-6DE54777B44B@.microsoft.com...
> SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced
Server. The server has 8 GB of RAM installed but for some reason SQL Server
is only utilizing less than 4 GB. What would the likely cause be?|||All those option is set. Still same problem
"John Oakes" wrote:

> Are you using the /3GB in your boot.ini? Look in books online under
> "Managing AWE Memory."
> -John Oakes
> "Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
> news:A4DAD1E0-5C6A-49D4-8631-6DE54777B44B@.microsoft.com...
> Server. The server has 8 GB of RAM installed but for some reason SQL Serve
r
> is only utilizing less than 4 GB. What would the likely cause be?
>
>|||Did you reboot after changing boot.ini?
-John Oakes
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:188FFB29-DDE5-42B3-A802-DC671FC7B68A@.microsoft.com...[vbcol=seagreen]
> All those option is set. Still same problem
> "John Oakes" wrote:
>
Advanced[vbcol=seagreen]
Server[vbcol=seagreen]|||You also need the /PAE set in the Boot.ini.
Andrew J. Kelly SQL MVP
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:188FFB29-DDE5-42B3-A802-DC671FC7B68A@.microsoft.com...[vbcol=seagreen]
> All those option is set. Still same problem
> "John Oakes" wrote:
>
Advanced[vbcol=seagreen]
Server[vbcol=seagreen]|||Serverdba wrote:

> SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced Server. T
he server has 8 GB of RAM installed but for some reason SQL Server is only utilizing
less than 4 GB. What would the likely cause be?
Hi,
The Account which starts the SQL Service must have the privilege "lock
pages in memory" - you can set this in the local policy settings

Tuesday, March 6, 2012

64-bit SQL Server for Xeon

Hello,
Is there a SQL Server 2000 64-bit Edition for XEON processors?
I saw that there are two different versions of SQL 2005 (64 Bit Extended and
64 Bit Itanium), but for SQL 2000 I found only one, and it seems that it's
for Itanium processors.
Thank youHi
SQL Server 2000 has only a full 64 bit edition of Itaniums.
SQL Server 2000 with SP4 supports EM64T and x64.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Vi" <Vi@.discussions.microsoft.com> wrote in message
news:8B3CC9AB-8025-4CDB-9B1D-4F0AC5DFFB8E@.microsoft.com...
> Hello,
> Is there a SQL Server 2000 64-bit Edition for XEON processors?
> I saw that there are two different versions of SQL 2005 (64 Bit Extended
> and
> 64 Bit Itanium), but for SQL 2000 I found only one, and it seems that it's
> for Itanium processors.
> Thank you|||So how do I install SQL 64-bit on a Xeon processor based server? Is there a
release "SQL 2000 with SP4"? And if so, is 64-bit an option during
installation?
Thanks
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> SQL Server 2000 has only a full 64 bit edition of Itaniums.
> SQL Server 2000 with SP4 supports EM64T and x64.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Vi" <Vi@.discussions.microsoft.com> wrote in message
> news:8B3CC9AB-8025-4CDB-9B1D-4F0AC5DFFB8E@.microsoft.com...
> > Hello,
> > Is there a SQL Server 2000 64-bit Edition for XEON processors?
> > I saw that there are two different versions of SQL 2005 (64 Bit Extended
> > and
> > 64 Bit Itanium), but for SQL 2000 I found only one, and it seems that it's
> > for Itanium processors.
> >
> > Thank you
>
>|||"Vi" <Vi@.discussions.microsoft.com> wrote in message
news:A329E111-A514-4860-9697-64F947441955@.microsoft.com...
> So how do I install SQL 64-bit on a Xeon processor based server? Is there
> a
> release "SQL 2000 with SP4"? And if so, is 64-bit an option during
> installation?
>
It's 32-bit SQL Server 2000 running in WOW32 mode on 64-bit windows. You
get a 4gig user-mode address space because of WOW64, but it's still a 32-bit
application.
David

64-bit SQL Server for Xeon

Hello,
Is there a SQL Server 2000 64-bit Edition for XEON processors?
I saw that there are two different versions of SQL 2005 (64 Bit Extended and
64 Bit Itanium), but for SQL 2000 I found only one, and it seems that it's
for Itanium processors.
Thank you
Hi
SQL Server 2000 has only a full 64 bit edition of Itaniums.
SQL Server 2000 with SP4 supports EM64T and x64.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Vi" <Vi@.discussions.microsoft.com> wrote in message
news:8B3CC9AB-8025-4CDB-9B1D-4F0AC5DFFB8E@.microsoft.com...
> Hello,
> Is there a SQL Server 2000 64-bit Edition for XEON processors?
> I saw that there are two different versions of SQL 2005 (64 Bit Extended
> and
> 64 Bit Itanium), but for SQL 2000 I found only one, and it seems that it's
> for Itanium processors.
> Thank you
|||So how do I install SQL 64-bit on a Xeon processor based server? Is there a
release "SQL 2000 with SP4"? And if so, is 64-bit an option during
installation?
Thanks
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> SQL Server 2000 has only a full 64 bit edition of Itaniums.
> SQL Server 2000 with SP4 supports EM64T and x64.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Vi" <Vi@.discussions.microsoft.com> wrote in message
> news:8B3CC9AB-8025-4CDB-9B1D-4F0AC5DFFB8E@.microsoft.com...
>
>
|||"Vi" <Vi@.discussions.microsoft.com> wrote in message
news:A329E111-A514-4860-9697-64F947441955@.microsoft.com...
> So how do I install SQL 64-bit on a Xeon processor based server? Is there
> a
> release "SQL 2000 with SP4"? And if so, is 64-bit an option during
> installation?
>
It's 32-bit SQL Server 2000 running in WOW32 mode on 64-bit windows. You
get a 4gig user-mode address space because of WOW64, but it's still a 32-bit
application.
David

64-bit SQL Server for Xeon

Hello,
Is there a SQL Server 2000 64-bit Edition for XEON processors?
I saw that there are two different versions of SQL 2005 (64 Bit Extended and
64 Bit Itanium), but for SQL 2000 I found only one, and it seems that it's
for Itanium processors.
Thank youHi
SQL Server 2000 has only a full 64 bit edition of Itaniums.
SQL Server 2000 with SP4 supports EM64T and x64.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Vi" <Vi@.discussions.microsoft.com> wrote in message
news:8B3CC9AB-8025-4CDB-9B1D-4F0AC5DFFB8E@.microsoft.com...
> Hello,
> Is there a SQL Server 2000 64-bit Edition for XEON processors?
> I saw that there are two different versions of SQL 2005 (64 Bit Extended
> and
> 64 Bit Itanium), but for SQL 2000 I found only one, and it seems that it's
> for Itanium processors.
> Thank you|||So how do I install SQL 64-bit on a Xeon processor based server? Is there a
release "SQL 2000 with SP4"? And if so, is 64-bit an option during
installation?
Thanks
"Mike Epprecht (SQL MVP)" wrote:

> Hi
> SQL Server 2000 has only a full 64 bit edition of Itaniums.
> SQL Server 2000 with SP4 supports EM64T and x64.
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "Vi" <Vi@.discussions.microsoft.com> wrote in message
> news:8B3CC9AB-8025-4CDB-9B1D-4F0AC5DFFB8E@.microsoft.com...
>
>|||"Vi" <Vi@.discussions.microsoft.com> wrote in message
news:A329E111-A514-4860-9697-64F947441955@.microsoft.com...
> So how do I install SQL 64-bit on a Xeon processor based server? Is there
> a
> release "SQL 2000 with SP4"? And if so, is 64-bit an option during
> installation?
>
It's 32-bit SQL Server 2000 running in WOW32 mode on 64-bit windows. You
get a 4gig user-mode address space because of WOW64, but it's still a 32-bit
application.
David

64bit SQL

Hi,
Can anyone confirm that the 64bit edition on SQL 2000 will only run on
Itanium 64 bit machines & not Xeon 64 bit processors?
Is there an Microsoft article on this?
Regards
SteveConfirmed.
(Don't know about MS article, haven't searched KB..)
On EM64T and 64 bit OS, you can run 32 bit SQL Server with sp4 in WOW, which
is supported, but
probably not what you want.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<stevanflores@.gmail.com> wrote in message
news:1142414594.177552.235650@.z34g2000cwc.googlegroups.com...
> Hi,
> Can anyone confirm that the 64bit edition on SQL 2000 will only run on
> Itanium 64 bit machines & not Xeon 64 bit processors?
> Is there an Microsoft article on this?
> Regards
> Steve
>|||Hi
Yes , 64bit runs on Itanium , but I don't remember the specific article
about that
<stevanflores@.gmail.com> wrote in message
news:1142414594.177552.235650@.z34g2000cwc.googlegroups.com...
> Hi,
> Can anyone confirm that the 64bit edition on SQL 2000 will only run on
> Itanium 64 bit machines & not Xeon 64 bit processors?
> Is there an Microsoft article on this?
> Regards
> Steve
>|||Thank you both.
We have a 32 bit application that is supposed be getting installed onto
64bit Server 2003, seeing as that we are still going to be using 32bit
SQL 2000, do you think it would be better for us to use the 32bit
version of Windows 2003?
Regards,
Steve|||IAE64 supports fully 64 bit and partially 32. Before this there was x64
allowing both architectures. As far as I know benefits (64) are visible when
you have more than 4 Gb RAM or 16 processors.
--
current location: alicante (es)
"Stevan" wrote:

> Thank you both.
> We have a 32 bit application that is supposed be getting installed onto
> 64bit Server 2003, seeing as that we are still going to be using 32bit
> SQL 2000, do you think it would be better for us to use the 32bit
> version of Windows 2003?
> Regards,
> Steve
>|||You should really look into using SQL2005 since you can run the 64 bit
edition of 2005 on Win2003 X64. But if you stay with 2000 then the 32 bit
is the only choice and it will run just fine on X64.
Andrew J. Kelly SQL MVP
"Stevan" <stevanflores@.gmail.com> wrote in message
news:1142415651.698599.131360@.e56g2000cwe.googlegroups.com...
> Thank you both.
> We have a 32 bit application that is supposed be getting installed onto
> 64bit Server 2003, seeing as that we are still going to be using 32bit
> SQL 2000, do you think it would be better for us to use the 32bit
> version of Windows 2003?
> Regards,
> Steve
>|||You can certainly run SQL2000 SP4 on Windows 2003 x64. And there are some
benefits right away. For instance, SQL2000 gets to use 4GB by default.
Whether these benefits will bobble up to your app level is a different story
.
The only way to determine whether using Windows 2003 x64 will provide better
performance for your app is for you to conduct some tests. For the workloads
I have tested, I get better performance on Windows 2003 x64 for some
workloads and no change in performance for the others >with Windows 2003 x86
vs x64 being the only variable<.
Linchi
"Stevan" wrote:

> Thank you both.
> We have a 32 bit application that is supposed be getting installed onto
> 64bit Server 2003, seeing as that we are still going to be using 32bit
> SQL 2000, do you think it would be better for us to use the 32bit
> version of Windows 2003?
> Regards,
> Steve
>|||stevanflores@.gmail.com wrote:
> Hi,
> Can anyone confirm that the 64bit edition on SQL 2000 will only run on
> Itanium 64 bit machines & not Xeon 64 bit processors?
> Is there an Microsoft article on this?
> Regards
> Steve
64-bit IA64 Itanium is your only 64-bit option for SQL Server 2000 and
it must run on equivalent Itanium hardware.
SQL Server 2005 supports three platforms: x86, x64 (AMD64 and Intel
EM64T), and Itanium
You can run SQL Server 2000 SP4 x86 and SQL Server 2005 x86 on Windows
Server 2003 x64 Edition.
David Gugick - SQL Server MVP
Quest Software

64bit SQL

Hi,
Can anyone confirm that the 64bit edition on SQL 2000 will only run on
Itanium 64 bit machines & not Xeon 64 bit processors?
Is there an Microsoft article on this?
Regards
SteveConfirmed.
(Don't know about MS article, haven't searched KB..)
On EM64T and 64 bit OS, you can run 32 bit SQL Server with sp4 in WOW, which is supported, but
probably not what you want.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<stevanflores@.gmail.com> wrote in message
news:1142414594.177552.235650@.z34g2000cwc.googlegroups.com...
> Hi,
> Can anyone confirm that the 64bit edition on SQL 2000 will only run on
> Itanium 64 bit machines & not Xeon 64 bit processors?
> Is there an Microsoft article on this?
> Regards
> Steve
>|||Hi
Yes , 64bit runs on Itanium , but I don't remember the specific article
about that
<stevanflores@.gmail.com> wrote in message
news:1142414594.177552.235650@.z34g2000cwc.googlegroups.com...
> Hi,
> Can anyone confirm that the 64bit edition on SQL 2000 will only run on
> Itanium 64 bit machines & not Xeon 64 bit processors?
> Is there an Microsoft article on this?
> Regards
> Steve
>|||Thank you both.
We have a 32 bit application that is supposed be getting installed onto
64bit Server 2003, seeing as that we are still going to be using 32bit
SQL 2000, do you think it would be better for us to use the 32bit
version of Windows 2003?
Regards,
Steve|||IAE64 supports fully 64 bit and partially 32. Before this there was x64
allowing both architectures. As far as I know benefits (64) are visible when
you have more than 4 Gb RAM or 16 processors.
--
current location: alicante (es)
"Stevan" wrote:
> Thank you both.
> We have a 32 bit application that is supposed be getting installed onto
> 64bit Server 2003, seeing as that we are still going to be using 32bit
> SQL 2000, do you think it would be better for us to use the 32bit
> version of Windows 2003?
> Regards,
> Steve
>|||You should really look into using SQL2005 since you can run the 64 bit
edition of 2005 on Win2003 X64. But if you stay with 2000 then the 32 bit
is the only choice and it will run just fine on X64.
--
Andrew J. Kelly SQL MVP
"Stevan" <stevanflores@.gmail.com> wrote in message
news:1142415651.698599.131360@.e56g2000cwe.googlegroups.com...
> Thank you both.
> We have a 32 bit application that is supposed be getting installed onto
> 64bit Server 2003, seeing as that we are still going to be using 32bit
> SQL 2000, do you think it would be better for us to use the 32bit
> version of Windows 2003?
> Regards,
> Steve
>|||You can certainly run SQL2000 SP4 on Windows 2003 x64. And there are some
benefits right away. For instance, SQL2000 gets to use 4GB by default.
Whether these benefits will bobble up to your app level is a different story.
The only way to determine whether using Windows 2003 x64 will provide better
performance for your app is for you to conduct some tests. For the workloads
I have tested, I get better performance on Windows 2003 x64 for some
workloads and no change in performance for the others >with Windows 2003 x86
vs x64 being the only variable<.
Linchi
"Stevan" wrote:
> Thank you both.
> We have a 32 bit application that is supposed be getting installed onto
> 64bit Server 2003, seeing as that we are still going to be using 32bit
> SQL 2000, do you think it would be better for us to use the 32bit
> version of Windows 2003?
> Regards,
> Steve
>|||stevanflores@.gmail.com wrote:
> Hi,
> Can anyone confirm that the 64bit edition on SQL 2000 will only run on
> Itanium 64 bit machines & not Xeon 64 bit processors?
> Is there an Microsoft article on this?
> Regards
> Steve
64-bit IA64 Itanium is your only 64-bit option for SQL Server 2000 and
it must run on equivalent Itanium hardware.
SQL Server 2005 supports three platforms: x86, x64 (AMD64 and Intel
EM64T), and Itanium
You can run SQL Server 2000 SP4 x86 and SQL Server 2005 x86 on Windows
Server 2003 x64 Edition.
David Gugick - SQL Server MVP
Quest Software

64bit SQL

Hi,
Can anyone confirm that the 64bit edition on SQL 2000 will only run on
Itanium 64 bit machines & not Xeon 64 bit processors?
Is there an Microsoft article on this?
Regards
Steve
Confirmed.
(Don't know about MS article, haven't searched KB..)
On EM64T and 64 bit OS, you can run 32 bit SQL Server with sp4 in WOW, which is supported, but
probably not what you want.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<stevanflores@.gmail.com> wrote in message
news:1142414594.177552.235650@.z34g2000cwc.googlegr oups.com...
> Hi,
> Can anyone confirm that the 64bit edition on SQL 2000 will only run on
> Itanium 64 bit machines & not Xeon 64 bit processors?
> Is there an Microsoft article on this?
> Regards
> Steve
>
|||Hi
Yes , 64bit runs on Itanium , but I don't remember the specific article
about that
<stevanflores@.gmail.com> wrote in message
news:1142414594.177552.235650@.z34g2000cwc.googlegr oups.com...
> Hi,
> Can anyone confirm that the 64bit edition on SQL 2000 will only run on
> Itanium 64 bit machines & not Xeon 64 bit processors?
> Is there an Microsoft article on this?
> Regards
> Steve
>
|||Thank you both.
We have a 32 bit application that is supposed be getting installed onto
64bit Server 2003, seeing as that we are still going to be using 32bit
SQL 2000, do you think it would be better for us to use the 32bit
version of Windows 2003?
Regards,
Steve
|||IAE64 supports fully 64 bit and partially 32. Before this there was x64
allowing both architectures. As far as I know benefits (64) are visible when
you have more than 4 Gb RAM or 16 processors.
current location: alicante (es)
"Stevan" wrote:

> Thank you both.
> We have a 32 bit application that is supposed be getting installed onto
> 64bit Server 2003, seeing as that we are still going to be using 32bit
> SQL 2000, do you think it would be better for us to use the 32bit
> version of Windows 2003?
> Regards,
> Steve
>
|||You should really look into using SQL2005 since you can run the 64 bit
edition of 2005 on Win2003 X64. But if you stay with 2000 then the 32 bit
is the only choice and it will run just fine on X64.
Andrew J. Kelly SQL MVP
"Stevan" <stevanflores@.gmail.com> wrote in message
news:1142415651.698599.131360@.e56g2000cwe.googlegr oups.com...
> Thank you both.
> We have a 32 bit application that is supposed be getting installed onto
> 64bit Server 2003, seeing as that we are still going to be using 32bit
> SQL 2000, do you think it would be better for us to use the 32bit
> version of Windows 2003?
> Regards,
> Steve
>
|||You can certainly run SQL2000 SP4 on Windows 2003 x64. And there are some
benefits right away. For instance, SQL2000 gets to use 4GB by default.
Whether these benefits will bobble up to your app level is a different story.
The only way to determine whether using Windows 2003 x64 will provide better
performance for your app is for you to conduct some tests. For the workloads
I have tested, I get better performance on Windows 2003 x64 for some
workloads and no change in performance for the others >with Windows 2003 x86
vs x64 being the only variable<.
Linchi
"Stevan" wrote:

> Thank you both.
> We have a 32 bit application that is supposed be getting installed onto
> 64bit Server 2003, seeing as that we are still going to be using 32bit
> SQL 2000, do you think it would be better for us to use the 32bit
> version of Windows 2003?
> Regards,
> Steve
>
|||stevanflores@.gmail.com wrote:
> Hi,
> Can anyone confirm that the 64bit edition on SQL 2000 will only run on
> Itanium 64 bit machines & not Xeon 64 bit processors?
> Is there an Microsoft article on this?
> Regards
> Steve
64-bit IA64 Itanium is your only 64-bit option for SQL Server 2000 and
it must run on equivalent Itanium hardware.
SQL Server 2005 supports three platforms: x86, x64 (AMD64 and Intel
EM64T), and Itanium
You can run SQL Server 2000 SP4 x86 and SQL Server 2005 x86 on Windows
Server 2003 x64 Edition.
David Gugick - SQL Server MVP
Quest Software

Saturday, February 25, 2012

64-Bit Edition for RS Database

I am attempting to install Reporting Services on a 32-bit application server
with the database on another box running SQL Server 2000 "Enterprise Edition
(64-bit)" . I am receiving the following error:
"This edition of the Report Server Database is not supported on the edition
of SQL Server 2000 you have chosen. Please choose ..."
The version I am attempting to install is "Reporting Services Enterprise
Edition". I've verified in the install window that it is the Enterprise
Edition of Reporting Services that I am trying to install. I have verified
that I can connect to the 64-bit server from my application server and my SQL
Login Account has SysAdmin permissions. I ran the SELECT
SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'),
SERVERPROPERTY ('edition') command that I read in another thread and it
returned the following information:
8.00.760 SP3 Enterprise Edition (64-bit)
I'm suspect that the "Enterprise Edition (64-bit)" is the culprit. Has
anyone installed Reporting Services using 64-bit SQL Server 2000 for the
database repository?
Thanks in advance...Setup will not allow you to install using a 64 bit version of SQL. There
are manual steps you can perform to get this to work, but it would require a
32 bit version of SQL.
1) Install RS pointing to the 32 bit version of SQL.
2) move both the ReportServer DB and the ReportServerTemp DB to the 64 bit
version (I don't know what the exact steps are to move a database from a 32
bit to a 64 bit sql, you would have to investigate this)
3) use rsconfig.exe to point RS to the 64 bit version of the catalog
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Malinda Jepsen" <Malinda Jepsen@.discussions.microsoft.com> wrote in message
news:E3DE691A-4A16-46CD-BE89-9964EE0FDCBA@.microsoft.com...
> I am attempting to install Reporting Services on a 32-bit application
server
> with the database on another box running SQL Server 2000 "Enterprise
Edition
> (64-bit)" . I am receiving the following error:
> "This edition of the Report Server Database is not supported on the
edition
> of SQL Server 2000 you have chosen. Please choose ..."
> The version I am attempting to install is "Reporting Services Enterprise
> Edition". I've verified in the install window that it is the Enterprise
> Edition of Reporting Services that I am trying to install. I have
verified
> that I can connect to the 64-bit server from my application server and my
SQL
> Login Account has SysAdmin permissions. I ran the SELECT
> SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'),
> SERVERPROPERTY ('edition') command that I read in another thread and it
> returned the following information:
> 8.00.760 SP3 Enterprise Edition (64-bit)
> I'm suspect that the "Enterprise Edition (64-bit)" is the culprit. Has
> anyone installed Reporting Services using 64-bit SQL Server 2000 for the
> database repository?
> Thanks in advance...|||Finally success!
What I found was that I couldn't pull a database from another install of
Reporting Services. Since I had already installed it in our lab environment
on a 32-bit server, I first tried to attach that database. But when I did
that, Reporting Services thought I wanted to join a web farm. Then when I
tried to install it with the .ini file with SQL authentication to create the
database (RSSETUPACCOUNT/RSSETUPPASSWORD), it was not creating the database
(even though the SQL user I was using had SysAdmin permissions). I finally
gave my NT account SysAdmin rights and then it would create the database
(using the default install without an .ini file). Once that was complete,
sure enough, I could just move it to the 64-bit server (using standard
detach/attach). One final step was to give the SQL (or NT) user permissions
in the database (I started with datareader and datawriter).
"Daniel Reib [MSFT]" wrote:
> Setup will not allow you to install using a 64 bit version of SQL. There
> are manual steps you can perform to get this to work, but it would require a
> 32 bit version of SQL.
> 1) Install RS pointing to the 32 bit version of SQL.
> 2) move both the ReportServer DB and the ReportServerTemp DB to the 64 bit
> version (I don't know what the exact steps are to move a database from a 32
> bit to a 64 bit sql, you would have to investigate this)
> 3) use rsconfig.exe to point RS to the 64 bit version of the catalog
>
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Malinda Jepsen" <Malinda Jepsen@.discussions.microsoft.com> wrote in message
> news:E3DE691A-4A16-46CD-BE89-9964EE0FDCBA@.microsoft.com...
> > I am attempting to install Reporting Services on a 32-bit application
> server
> > with the database on another box running SQL Server 2000 "Enterprise
> Edition
> > (64-bit)" . I am receiving the following error:
> > "This edition of the Report Server Database is not supported on the
> edition
> > of SQL Server 2000 you have chosen. Please choose ..."
> >
> > The version I am attempting to install is "Reporting Services Enterprise
> > Edition". I've verified in the install window that it is the Enterprise
> > Edition of Reporting Services that I am trying to install. I have
> verified
> > that I can connect to the 64-bit server from my application server and my
> SQL
> > Login Account has SysAdmin permissions. I ran the SELECT
> > SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'),
> > SERVERPROPERTY ('edition') command that I read in another thread and it
> > returned the following information:
> > 8.00.760 SP3 Enterprise Edition (64-bit)
> >
> > I'm suspect that the "Enterprise Edition (64-bit)" is the culprit. Has
> > anyone installed Reporting Services using 64-bit SQL Server 2000 for the
> > database repository?
> >
> > Thanks in advance...
>
>

64-bit and SQL Server

If I want to use SQL Server and 64-bit, do I need
Enterprise Edition or can I use it ony SQL Server SE?AFAIK, then you buy 64 bit, the only edition available is 64 bit.
--
Tibor Karaszi
"Paul Z" <paulz_ibm@.msn.com> wrote in message
news:0f3301c3a3ac$fa1b9580$a401280a@.phx.gbl...
> If I want to use SQL Server and 64-bit, do I need
> Enterprise Edition or can I use it ony SQL Server SE?|||That should have been:
AFAIK, then you buy 64 bit, the only edition available is Enterprise
Edition.
Tibor Karaszi
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se>
wrote in message news:ij8qb.36638$dP1.122710@.newsc.telia.net...
> AFAIK, then you buy 64 bit, the only edition available is 64 bit.
> --
> Tibor Karaszi
>
> "Paul Z" <paulz_ibm@.msn.com> wrote in message
> news:0f3301c3a3ac$fa1b9580$a401280a@.phx.gbl...
> > If I want to use SQL Server and 64-bit, do I need
> > Enterprise Edition or can I use it ony SQL Server SE?
>

64 bit windows 2003 sp2 SQL SERVER 2005 Linked server

The server is IBM XS 466.
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
Standing on Shoulders of Giants
* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse
|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
That should get things in working order.
Jesse
|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
Standing on Shoulders of Giants
"Jesse Houwing" wrote:

> * fds2003 wrote, On 4-7-2007 12:32:
> You can find the 64-bit OleDB Driver here:
> http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
> That should get things in working order.
> Jesse
>

64 bit windows 2003 sp2 SQL SERVER 2005 Linked server

The server is IBM XS 466.
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
--
Standing on Shoulders of Giants* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACL
E
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACL
E
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
[url]http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html[/u
rl]
That should get things in working order.
Jesse|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
--
Standing on Shoulders of Giants
"Jesse Houwing" wrote:

> * fds2003 wrote, On 4-7-2007 12:32:
> You can find the 64-bit OleDB Driver here:
> [url]http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html[
/url]
> That should get things in working order.
> Jesse
>

64 bit windows 2003 sp2 SQL SERVER 2005 Linked server

The server is IBM XS 466.
The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
(64bit),I want to create a linked server for Oracle,I have installed ORACLE
Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
2005,i can't find 'MSDAORA',it caust i can't create linked server for
oracle.msbut I can find some drivers about oracle in ODBC,but must run
'c:\windows\system32\odbcad32.exe'
This proble puzzle me for some days
--
Standing on Shoulders of Giants* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
My first guess is that the 64 version of SQL Server can only load 64-bit
drivers. This means the old OleDb driver and ODBC driver are not
compatible.
Either reinstall SQL server as 32-bit binaries or find a 64-bit
compatible driver for Oracle.
Jesse|||* fds2003 wrote, On 4-7-2007 12:32:
> The server is IBM XS 466.
> The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> oracle.msbut I can find some drivers about oracle in ODBC,but must run
> 'c:\windows\system32\odbcad32.exe'
> This proble puzzle me for some days
You can find the 64-bit OleDB Driver here:
http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
That should get things in working order.
Jesse|||I haved installed 64bit Driver for Oracle,but the proble is the same,it has
other approach?
--
Standing on Shoulders of Giants
"Jesse Houwing" wrote:
> * fds2003 wrote, On 4-7-2007 12:32:
> > The server is IBM XS 466.
> > The server is Windows 2003 R2 64 bit with SQL 2005 SP2 Enterprise Edition
> > (64bit),I want to create a linked server for Oracle,I have installed ORACLE
> > Client 10g(64bit) ,but I can't find any drivers about oracle in SQL SERVER
> > 2005,i can't find 'MSDAORA',it caust i can't create linked server for
> > oracle.msbut I can find some drivers about oracle in ODBC,but must run
> > 'c:\windows\system32\odbcad32.exe'
> > This proble puzzle me for some days
> You can find the 64-bit OleDB Driver here:
> http://www.oracle.com/technology/software/tech/windows/odpnet/64-bit/index.html
> That should get things in working order.
> Jesse
>

Friday, February 24, 2012

64 bit memory and AWE ?

Hi There

I have installed 64 bit Standard Edition SS 2005 on a 64 bit WOndows Server 2003 R2 platform.

When i go to Memory setting for this instance i set max server memory to 6 Gig.

I am presuming i do not have to enable AWE, sicne everything is 64 bit.

Is this correct ?

Thanx

AWE is used for 32-bit OS due to 32-bit system can only address 4GB memory in conventual way, so it need to set /PAE in boot.ini file and set AWE enabled in SQL server.

but for 64-bit OS and SQL server (both 2000 and 2005) do not need to set this option.