3G ram for SQL server: enterprise

Showing posts with label enterprise. Show all posts

Tuesday, March 27, 2012

A feature available in oracle, is it available in sql server?

Theres a feature in oracle that allows you to modify tables, colums, values and the data from its enterprise console the same way that you can in sql server. In oracle however theres a button called 'show sql' that allows you to see and copy/paste the resulting sql for the changes made via the console.

I would imagine that sql server has a similar option. The reason i ask is that i would like to more fully learn how to do this through the query analyser and get more familiar with sql involved and I would be able to do this if I could see the resulting sql from enterprise manager.

Hope this makes sense.

I did find something in sql server called 'generate sql' but this doesnt update during changes you make automatically.

Thanksyeah if you have downloaded ther BOL ( which you should) look for ALTER TABLE key word. you can add columns, drop 'em modify 'em etc.

hth|||Thanks for the reply. But, whats the BOL. And what are you talking about?!>?! This doesnt answer my question. I'm talking about the ability to see the resulting sql when modifying it in the enterprise console.|||What you are looking for is called "Save Change Script".

If you are in Enterprise Manager, right click on a table name, and choose "Design". This will take you into the Design Table interface. If you hover over the 3rd icon from the left you will see that it says "save change script" (note that you actually have to make a change in order for this to become active). If you click on this you will see the exact commands that EM is going to execute to accomomdate your changes, and you can opt to save them to disk.

Also, BOL is Books Online, an invaluable free SQL Server reference from Microsoft. It is a huge download but well worth it. You can find it here:SQL Server 2000 Books Online (Updated 2004).

Terri

Tuesday, March 20, 2012

a bug in Enterprise Manager ?

if I use enterprise manager to change Login permissions, I
am prompted to confirm the password even if the password
is not changed. Worse thing is that most of the time I
don't know the login password , so I am not able use EM to
assign permissions. I have access to other computers with
SQL EM working, and if I need to I can still use QA. I use
my pc for most of the sql admin work and would like if I
can resolve this.
What should I do ?
Thanks in advanceSee if this helps:
FIX: You Are Prompted for Password Confirmation After You Change a Standard
SQL Server Login
http://support.microsoft.com/default.aspx?scid=kb;en-us;826161&Product=sql2k
Rand
This posting is provided "as is" with no warranties and confers no rights.

a bug in Enterprise Manager ?

if I use enterprise manager to change Login permissions, I
am prompted to confirm the password even if the password
is not changed. Worse thing is that most of the time I
don't know the login password , so I am not able use EM to
assign permissions. I have access to other computers with
SQL EM working, and if I need to I can still use QA. I use
my pc for most of the sql admin work and would like if I
can resolve this.
What should I do ?
Thanks in advance
See if this helps:
FIX: You Are Prompted for Password Confirmation After You Change a Standard
SQL Server Login
http://support.microsoft.com/default...&Product=sql2k
Rand
This posting is provided "as is" with no warranties and confers no rights.

a bug in Enterprise Manager ?

if I use enterprise manager to change Login permissions, I
am prompted to confirm the password even if the password
is not changed. Worse thing is that most of the time I
don't know the login password , so I am not able use EM to
assign permissions. I have access to other computers with
SQL EM working, and if I need to I can still use QA. I use
my pc for most of the sql admin work and would like if I
can resolve this.
What should I do ?
Thanks in advanceSee if this helps:
FIX: You Are Prompted for Password Confirmation After You Change a Standard
SQL Server Login
http://support.microsoft.com/defaul...1&Product=sql2k
Rand
This posting is provided "as is" with no warranties and confers no rights.

a better Enterprise Manager plz

hi,
do u know some nice (preferably commersial) tool for SQL Server 2k
administration
Embarcadero DBArtisan 8.0 (current).
"Coldman" wrote:

> hi,
> do u know some nice (preferably commersial) tool for SQL Server 2k
> administration
>
>
|||tnx, Julia, i`ll try it
"Julia" <Julia@.discussions.microsoft.com> wrote in message
news:01FAB6BB-7431-4F0D-9CE4-FFCD62BB2BD5@.microsoft.com...[vbcol=seagreen]
> Embarcadero DBArtisan 8.0 (current).
> "Coldman" wrote:
|||Hi,
DBArtsan is a good tool for Oracle/DB2 and Sybase. But as far as SQL Server
is concerned Enterprise manager is the best for
doing basic administration.
Thanks
Hari
SQL Server MVP
"Coldman" <nomorespam@.mail.com> wrote in message
news:OJbRR$KrFHA.2604@.TK2MSFTNGP14.phx.gbl...
> hi,
> do u know some nice (preferably commersial) tool for SQL Server 2k
> administration
>
sql

a better Enterprise Manager plz

hi,
do u know some nice (preferably commersial) tool for SQL Server 2k
administrationEmbarcadero DBArtisan 8.0 (current).
"Coldman" wrote:

> hi,
> do u know some nice (preferably commersial) tool for SQL Server 2k
> administration
>
>|||tnx, Julia, i`ll try it
"Julia" <Julia@.discussions.microsoft.com> wrote in message
news:01FAB6BB-7431-4F0D-9CE4-FFCD62BB2BD5@.microsoft.com...[vbcol=seagreen]
> Embarcadero DBArtisan 8.0 (current).
> "Coldman" wrote:
>|||Hi,
DBArtsan is a good tool for Oracle/DB2 and Sybase. But as far as SQL Server
is concerned Enterprise manager is the best for
doing basic administration.
Thanks
Hari
SQL Server MVP
"Coldman" <nomorespam@.mail.com> wrote in message
news:OJbRR$KrFHA.2604@.TK2MSFTNGP14.phx.gbl...
> hi,
> do u know some nice (preferably commersial) tool for SQL Server 2k
> administration
>

a better Enterprise Manager plz

hi,
do u know some nice (preferably commersial) tool for SQL Server 2k
administrationEmbarcadero DBArtisan 8.0 (current).
"Coldman" wrote:
> hi,
> do u know some nice (preferably commersial) tool for SQL Server 2k
> administration
>
>|||tnx, Julia, i`ll try it
"Julia" <Julia@.discussions.microsoft.com> wrote in message
news:01FAB6BB-7431-4F0D-9CE4-FFCD62BB2BD5@.microsoft.com...
> Embarcadero DBArtisan 8.0 (current).
> "Coldman" wrote:
>> hi,
>> do u know some nice (preferably commersial) tool for SQL Server 2k
>> administration
>>|||Hi,
DBArtsan is a good tool for Oracle/DB2 and Sybase. But as far as SQL Server
is concerned Enterprise manager is the best for
doing basic administration.
Thanks
Hari
SQL Server MVP
"Coldman" <nomorespam@.mail.com> wrote in message
news:OJbRR$KrFHA.2604@.TK2MSFTNGP14.phx.gbl...
> hi,
> do u know some nice (preferably commersial) tool for SQL Server 2k
> administration
>

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
> >
> >
> >.
> >

8GB memory installation

Situation:
OS: 2000 advanced server
SQL enterprise
We have just added an extra 6GB of memory to our database server which
brings the total to 8. The problem we are having is that the OS is only using
3Gb of memory.
We have run the SP that is recommended for AWE and entered the /3GB /PAE in
the boot.ini file and restarted the machine.
The server still refuses to use more than 3GB. Any ideas?Did you re-configure SQL, the AWE and fixed memory?
e.g.
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'min server memory', 6656 (make same as maximum)
RECONFIGURE
go
sp_configure 'max server memory', 6656 (leave at least 512 for the OS)
RECONFIGURE
Regards
Mike
"lramsdale" wrote:
> Situation:
> OS: 2000 advanced server
> SQL enterprise
> We have just added an extra 6GB of memory to our database server which
> brings the total to 8. The problem we are having is that the OS is only using
> 3Gb of memory.
> We have run the SP that is recommended for AWE and entered the /3GB /PAE in
> the boot.ini file and restarted the machine.
> The server still refuses to use more than 3GB. Any ideas?|||This is what we ran:
sp_configure 'show advanced options', 1
RECONFIGURE
GO
sp_configure 'awe enabled', 1
RECONFIGURE
GO
sp_configure 'max server memory', 6144
RECONFIGURE
GO
"Mike Epprecht (SQL MVP)" wrote:
> Did you re-configure SQL, the AWE and fixed memory?
> e.g.
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'min server memory', 6656 (make same as maximum)
> RECONFIGURE
> go
> sp_configure 'max server memory', 6656 (leave at least 512 for the OS)
> RECONFIGURE
> Regards
> Mike
> "lramsdale" wrote:
> > Situation:
> >
> > OS: 2000 advanced server
> > SQL enterprise
> >
> > We have just added an extra 6GB of memory to our database server which
> > brings the total to 8. The problem we are having is that the OS is only using
> > 3Gb of memory.
> >
> > We have run the SP that is recommended for AWE and entered the /3GB /PAE in
> > the boot.ini file and restarted the machine.
> >
> > The server still refuses to use more than 3GB. Any ideas?|||Ok we finally got to the bottom of this problem - it seems that we needed to
give the SQL server service account permissions to the lock pages in memory
privelege, even though it was in the domain admin account. This was hard to
find, why is there so much conflicting documentation on this AWE setting?
"lramsdale" wrote:
> This is what we ran:
> sp_configure 'show advanced options', 1
> RECONFIGURE
> GO
> sp_configure 'awe enabled', 1
> RECONFIGURE
> GO
> sp_configure 'max server memory', 6144
> RECONFIGURE
> GO
> "Mike Epprecht (SQL MVP)" wrote:
> > Did you re-configure SQL, the AWE and fixed memory?
> >
> > e.g.
> >
> > sp_configure 'show advanced options', 1
> > RECONFIGURE
> > GO
> > sp_configure 'awe enabled', 1
> > RECONFIGURE
> > GO
> > sp_configure 'min server memory', 6656 (make same as maximum)
> > RECONFIGURE
> > go
> > sp_configure 'max server memory', 6656 (leave at least 512 for the OS)
> > RECONFIGURE
> >
> > Regards
> > Mike
> >
> > "lramsdale" wrote:
> >
> > > Situation:
> > >
> > > OS: 2000 advanced server
> > > SQL enterprise
> > >
> > > We have just added an extra 6GB of memory to our database server which
> > > brings the total to 8. The problem we are having is that the OS is only using
> > > 3Gb of memory.
> > >
> > > We have run the SP that is recommended for AWE and entered the /3GB /PAE in
> > > the boot.ini file and restarted the machine.
> > >
> > > The server still refuses to use more than 3GB. Any ideas?

Sunday, March 11, 2012

'8007007F' error

Hi,
I have a problem with my SQL Server 2000.
When I try to display the rows from a table with enterprise manager, I get a
'8007007F' error
I don't have this problem if I read the table from a Query using the Query
Anlyzer.
I use Windows 2003 Server and I installed the MDAC 8.x
This problem also occurs when I try to open databases from Active Server
pages
Any ideas ?
Stan.I'm experiencing the same issues after upgrading from Windows Server 2000 to
Windows Server 2003. I receive error '8007007F' when i try to query an ASP
page|||Hi Shaheen,
My problem was not a ASP problem but a DLL problem
I was not able to view my datatable with Enterprise Manager.
If you have the same problem in this case, check this url out.
http://groups.google.com/groups?q=%...0phx.gbl&rnum=1
Hope that helps.
Stan
"Shaheen" <anonymous@.discussions.microsoft.com> a crit dans le message de
news:AE4ADF75-0850-4D7D-9488-EF484AFC77A3@.microsoft.com...
> I'm experiencing the same issues after upgrading from Windows Server 2000
to Windows Server 2003. I receive error '8007007F' when i try to query an
ASP page|||I had the same problem after upgrading to Windows 2003 Server. I called Mic
rosoft and here is the fix:
Symptoms:
After upgrading from Windows 2000 to Windows 2003 attempting to access a dat
abase or data component will result in a '8007007f' or "The specified proced
ure could not be found" error.
Status:
This is a known issue with some installations of Windows 2003
Workaround:
Extract oledb32.dll from the zip file into these two directories. It's impo
rtant that it be done in this order:
1) C:\WINNT\system32\dllCache
2) C:\Program Files\Common Files\System\OLE DB
3) Reboot the server
Cause:
This issue is caused when the Windows 2003 installer did not update the oled
b32.dll file.
You can dowload the oledb32.dll file here: [url]http://www.promiseweb.com/oledb32
.zip[/
url]
This is per Malcolm Stewart at Microsoft Developer Support

'8007007F' error

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

8 GB of RAM

I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
Standard.
I have the switches /PAE /3GB in boot.ini
SQL max server memory is = 6656 MB
but with those settings I cannot get SQLServer to get more than 2.7 GB
of RAM
If I use the AWE switch, then SQLServer can only use 128 MB max
What's wrong?
PaulOn Dec 4, 3:42 am, pd...@.clic.net wrote:
> I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> Standard.
> I have the switches /PAE /3GB in boot.ini
> SQL max server memory is = 6656 MB
> but with those settings I cannot get SQLServer to get more than 2.7 GB
> of RAM
> If I use the AWE switch, then SQLServer can only use 128 MB max
> What's wrong?
> Paul
Is it SQL Server 2000 or SQL Server 2005?
If its SQL Server 2000, then AWE is not supported
If its SQL Server 2005, then check the AWE 'Run Value' in
sp_configure... if its 0, then you might want to recycle the SQL
Server service to enable the AWE
In any case i dont believe you need to have /3GB switch in boot.ini.|||Hey, of course you can use AWE on SQL Server 2000 (and also on SQL Server
2005).
You will need to run
sp_configure 'awe enabled', 1
and grant the Lock Page in Memory permission to your service account. For
more details see
How to configure SQL Server to use more than 2 GB of physical memory
http://support.microsoft.com/kb/274750
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"dineshbabu.munugala@.gmail.com" wrote:
> On Dec 4, 3:42 am, pd...@.clic.net wrote:
> > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> > Standard.
> > I have the switches /PAE /3GB in boot.ini
> >
> > SQL max server memory is = 6656 MB
> >
> > but with those settings I cannot get SQLServer to get more than 2.7 GB
> > of RAM
> >
> > If I use the AWE switch, then SQLServer can only use 128 MB max
> >
> > What's wrong?
> >
> > Paul
> Is it SQL Server 2000 or SQL Server 2005?
> If its SQL Server 2000, then AWE is not supported
> If its SQL Server 2005, then check the AWE 'Run Value' in
> sp_configure... if its 0, then you might want to recycle the SQL
> Server service to enable the AWE
> In any case i dont believe you need to have /3GB switch in boot.ini.
>|||Ben
If you are on 64-bit , you do not need AWE anymore. If the OP has SQL Server
2000 along with SP4 , make sure that he has a last hotfix especially if he
are going to enable AWE
"Ben Nevarez" <BenNevarez@.discussions.microsoft.com> wrote in message
news:2ADA35D9-C4FA-4852-B20A-3E08F240C626@.microsoft.com...
> Hey, of course you can use AWE on SQL Server 2000 (and also on SQL Server
> 2005).
> You will need to run
> sp_configure 'awe enabled', 1
> and grant the Lock Page in Memory permission to your service account. For
> more details see
> How to configure SQL Server to use more than 2 GB of physical memory
> http://support.microsoft.com/kb/274750
> Hope this helps,
> Ben Nevarez
> Senior Database Administrator
> AIG SunAmerica
>
> "dineshbabu.munugala@.gmail.com" wrote:
>> On Dec 4, 3:42 am, pd...@.clic.net wrote:
>> > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
>> > Standard.
>> > I have the switches /PAE /3GB in boot.ini
>> >
>> > SQL max server memory is = 6656 MB
>> >
>> > but with those settings I cannot get SQLServer to get more than 2.7 GB
>> > of RAM
>> >
>> > If I use the AWE switch, then SQLServer can only use 128 MB max
>> >
>> > What's wrong?
>> >
>> > Paul
>> Is it SQL Server 2000 or SQL Server 2005?
>> If its SQL Server 2000, then AWE is not supported
>> If its SQL Server 2005, then check the AWE 'Run Value' in
>> sp_configure... if its 0, then you might want to recycle the SQL
>> Server service to enable the AWE
>> In any case i dont believe you need to have /3GB switch in boot.ini.|||On 3 d=E9c, 18:04, dineshbabu.munug...@.gmail.com wrote:
> On Dec 4, 3:42 am, pd...@.clic.net wrote:
> > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> > Standard.
> > I have the switches /PAE /3GB in boot.ini
> > SQL max server memory is =3D 6656 MB
> > but with those settings I cannot get SQLServer to get more than 2.7 GB
> > of RAM
> > If I use the AWE switch, then SQLServer can only use 128 MB max
> > What's wrong?
> > Paul
> Is it SQL Server 2000 or SQL Server 2005?
> If its SQL Server 2000, then AWE is not supported
> If its SQL Server 2005, then check the AWE 'Run Value' in
> sp_configure... if its 0, then you might want to recycle the SQL
> Server service to enable the AWE
> In any case i dont believe you need to have /3GB switch in boot.ini.
SQL2005 Standard.
Running in 32 bits system
As soon as I use AWE, I'm stuck with 128 MB of RAM for SQL server...
(i.e. I run dbcc checkDB so that it starts using rapidly memory and I
see SQLServer.exe using not more than 128 MB of RAM in Task Manager).
Paul|||Hi
Do you have SP4 with hotfix?
Install hotfix from(http://support.microsoft.com/kb/899761)
Do you see in PerfMon that SQL Server allocate 6.6GB RAM?
<pdube@.clic.net> wrote in message
news:e4a9b19a-1b95-4df7-b6d9-e8c374bfb9c0@.a39g2000pre.googlegroups.com...
On 3 déc, 18:04, dineshbabu.munug...@.gmail.com wrote:
> On Dec 4, 3:42 am, pd...@.clic.net wrote:
> > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> > Standard.
> > I have the switches /PAE /3GB in boot.ini
> > SQL max server memory is = 6656 MB
> > but with those settings I cannot get SQLServer to get more than 2.7 GB
> > of RAM
> > If I use the AWE switch, then SQLServer can only use 128 MB max
> > What's wrong?
> > Paul
> Is it SQL Server 2000 or SQL Server 2005?
> If its SQL Server 2000, then AWE is not supported
> If its SQL Server 2005, then check the AWE 'Run Value' in
> sp_configure... if its 0, then you might want to recycle the SQL
> Server service to enable the AWE
> In any case i dont believe you need to have /3GB switch in boot.ini.
SQL2005 Standard.
Running in 32 bits system
As soon as I use AWE, I'm stuck with 128 MB of RAM for SQL server...
(i.e. I run dbcc checkDB so that it starts using rapidly memory and I
see SQLServer.exe using not more than 128 MB of RAM in Task Manager).
Paul|||On 4 d=E9c, 10:45, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Hi
> Do you have SP4 with hotfix?
> Install hotfix from(http://support.microsoft.com/kb/899761)
> Do you see in PerfMon that SQL Server allocate 6.6GB RAM?
> <pd...@.clic.net> wrote in message
> news:e4a9b19a-1b95-4df7-b6d9-e8c374bfb9c0@.a39g2000pre.googlegroups.com...
> On 3 d=E9c, 18:04, dineshbabu.munug...@.gmail.com wrote:
>
>
> > On Dec 4, 3:42 am, pd...@.clic.net wrote:
> > > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> > > Standard.
> > > I have the switches /PAE /3GB in boot.ini
> > > SQL max server memory is =3D 6656 MB
> > > but with those settings I cannot get SQLServer to get more than 2.7 GB=
> > > of RAM
> > > If I use the AWE switch, then SQLServer can only use 128 MB max
> > > What's wrong?
> > > Paul
> > Is it SQL Server 2000 or SQL Server 2005?
> > If its SQL Server 2000, then AWE is not supported
> > If its SQL Server 2005, then check the AWE 'Run Value' in
> > sp_configure... if its 0, then you might want to recycle the SQL
> > Server service to enable the AWE
> > In any case i dont believe you need to have /3GB switch in boot.ini.
> SQL2005 Standard.
> Running in 32 bits system
> As soon as I use AWE, I'm stuck with 128 MB of RAM for SQL server...
> (i.e. I run dbcc checkDB so that it starts using rapidly memory and I
> see SQLServer.exe using not more than 128 MB of RAM in Task Manager).
> Paul- Masquer le texte des messages pr=E9c=E9dents -
> - Afficher le texte des messages pr=E9c=E9dents -
SQL 2005 (9.00.3161.00)
The hotfix is for SQL 2000...
In PerfMon, I see Commited Bytes around 3.2 GB.
In Task Manager I still see SQLServer.exe using 2.7 GB. I guess then
that's just a problem related with Task Manager not showing the
correct amount of RAM used...?
Paul|||On 4 d=E9c, 14:08, pd...@.clic.net wrote:
> On 4 d=E9c, 10:45, "Uri Dimant" <u...@.iscar.co.il> wrote:
>
>
> > Hi
> > Do you have SP4 with hotfix?
> > Install hotfix from(http://support.microsoft.com/kb/899761)
> > Do you see in PerfMon that SQL Server allocate 6.6GB RAM?
> > <pd...@.clic.net> wrote in message
> >news:e4a9b19a-1b95-4df7-b6d9-e8c374bfb9c0@.a39g2000pre.googlegroups.com...=
> > On 3 d=E9c, 18:04, dineshbabu.munug...@.gmail.com wrote:
> > > On Dec 4, 3:42 am, pd...@.clic.net wrote:
> > > > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server=
> > > > Standard.
> > > > I have the switches /PAE /3GB in boot.ini
> > > > SQL max server memory is =3D 6656 MB
> > > > but with those settings I cannot get SQLServer to get more than 2.7 =GB
> > > > of RAM
> > > > If I use the AWE switch, then SQLServer can only use 128 MB max
> > > > What's wrong?
> > > > Paul
> > > Is it SQL Server 2000 or SQL Server 2005?
> > > If its SQL Server 2000, then AWE is not supported
> > > If its SQL Server 2005, then check the AWE 'Run Value' in
> > > sp_configure... if its 0, then you might want to recycle the SQL
> > > Server service to enable the AWE
> > > In any case i dont believe you need to have /3GB switch in boot.ini.
> > SQL2005 Standard.
> > Running in 32 bits system
> > As soon as I use AWE, I'm stuck with 128 MB of RAM for SQL server...
> > (i.e. I run dbcc checkDB so that it starts using rapidly memory and I
> > see SQLServer.exe using not more than 128 MB of RAM in Task Manager).
> > Paul- Masquer le texte des messages pr=E9c=E9dents -
> > - Afficher le texte des messages pr=E9c=E9dents -
> SQL 2005 (9.00.3161.00)
> The hotfix is for SQL 2000...
> In PerfMon, I see Commited Bytes around 3.2 GB.
> In Task Manager I still see SQLServer.exe using 2.7 GB. I guess then
> that's just a problem related with Task Manager not showing the
> correct amount of RAM used...?
> Paul- Masquer le texte des messages pr=E9c=E9dents -
> - Afficher le texte des messages pr=E9c=E9dents -
When I say that I see 128 MB of RAM in SQLServer.exe when using AWE I
mean that's what I see in Task Manager. Am I correct looking at this
value?
Should I check PerfMon instead? Is the memory shown in TaskManager
only kernel memory and would not show all memory used by SQL?
Paul|||SP4 hotfix is not needed here as this is SQL Server 2005.
Try this to see how much memory SQL Server is using. Performance Monitor,
add SQLServer:Memory Manager - Total Server Memory (KB).
Have you granted the Lock Page in Memory permission to your service account?
See your Error log. Must show 'Address Windowing Extensions enabled' or some
AWE error message.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"Uri Dimant" wrote:
> Hi
> Do you have SP4 with hotfix?
> Install hotfix from(http://support.microsoft.com/kb/899761)
> Do you see in PerfMon that SQL Server allocate 6.6GB RAM?
>
>
> <pdube@.clic.net> wrote in message
> news:e4a9b19a-1b95-4df7-b6d9-e8c374bfb9c0@.a39g2000pre.googlegroups.com...
> On 3 dÃ©c, 18:04, dineshbabu.munug...@.gmail.com wrote:
> > On Dec 4, 3:42 am, pd...@.clic.net wrote:
> >
> > > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> > > Standard.
> > > I have the switches /PAE /3GB in boot.ini
> >
> > > SQL max server memory is = 6656 MB
> >
> > > but with those settings I cannot get SQLServer to get more than 2.7 GB
> > > of RAM
> >
> > > If I use the AWE switch, then SQLServer can only use 128 MB max
> >
> > > What's wrong?
> >
> > > Paul
> >
> > Is it SQL Server 2000 or SQL Server 2005?
> > If its SQL Server 2000, then AWE is not supported
> > If its SQL Server 2005, then check the AWE 'Run Value' in
> > sp_configure... if its 0, then you might want to recycle the SQL
> > Server service to enable the AWE
> >
> > In any case i dont believe you need to have /3GB switch in boot.ini.
> SQL2005 Standard.
> Running in 32 bits system
> As soon as I use AWE, I'm stuck with 128 MB of RAM for SQL server...
> (i.e. I run dbcc checkDB so that it starts using rapidly memory and I
> see SQLServer.exe using not more than 128 MB of RAM in Task Manager).
> Paul
>
>|||Sorry. I missed that you are on SQL Server 2005.
In 32 -bit you do need AWE and as Ben pointed out gran permission Lock
Page in Memory permission to your service account.
To see if SQL server uses 6GB open PerfMonitor , do not use Task Manager
Visit also http://blogs.msdn.com/slavao/
<pdube@.clic.net> wrote in message
news:f9c9559b-d836-4b7f-92d4-bfc8834aab35@.s36g2000prg.googlegroups.com...
On 4 déc, 14:08, pd...@.clic.net wrote:
> On 4 déc, 10:45, "Uri Dimant" <u...@.iscar.co.il> wrote:
>
>
> > Hi
> > Do you have SP4 with hotfix?
> > Install hotfix from(http://support.microsoft.com/kb/899761)
> > Do you see in PerfMon that SQL Server allocate 6.6GB RAM?
> > <pd...@.clic.net> wrote in message
> >news:e4a9b19a-1b95-4df7-b6d9-e8c374bfb9c0@.a39g2000pre.googlegroups.com...
> > On 3 déc, 18:04, dineshbabu.munug...@.gmail.com wrote:
> > > On Dec 4, 3:42 am, pd...@.clic.net wrote:
> > > > I am running Windows 2003 Enterprise with 8 GB of RAM and SQL Server
> > > > Standard.
> > > > I have the switches /PAE /3GB in boot.ini
> > > > SQL max server memory is = 6656 MB
> > > > but with those settings I cannot get SQLServer to get more than 2.7
> > > > GB
> > > > of RAM
> > > > If I use the AWE switch, then SQLServer can only use 128 MB max
> > > > What's wrong?
> > > > Paul
> > > Is it SQL Server 2000 or SQL Server 2005?
> > > If its SQL Server 2000, then AWE is not supported
> > > If its SQL Server 2005, then check the AWE 'Run Value' in
> > > sp_configure... if its 0, then you might want to recycle the SQL
> > > Server service to enable the AWE
> > > In any case i dont believe you need to have /3GB switch in boot.ini.
> > SQL2005 Standard.
> > Running in 32 bits system
> > As soon as I use AWE, I'm stuck with 128 MB of RAM for SQL server...
> > (i.e. I run dbcc checkDB so that it starts using rapidly memory and I
> > see SQLServer.exe using not more than 128 MB of RAM in Task Manager).
> > Paul- Masquer le texte des messages précédents -
> > - Afficher le texte des messages précédents -
> SQL 2005 (9.00.3161.00)
> The hotfix is for SQL 2000...
> In PerfMon, I see Commited Bytes around 3.2 GB.
> In Task Manager I still see SQLServer.exe using 2.7 GB. I guess then
> that's just a problem related with Task Manager not showing the
> correct amount of RAM used...?
> Paul- Masquer le texte des messages précédents -
> - Afficher le texte des messages précédents -
When I say that I see 128 MB of RAM in SQLServer.exe when using AWE I
mean that's what I see in Task Manager. Am I correct looking at this
value?
Should I check PerfMon instead? Is the memory shown in TaskManager
only kernel memory and would not show all memory used by SQL?
Paul

8 GB of RAM

Tuesday, March 6, 2012

64-bit SQL2000 on 32-bit OS

Will my SQL server work like 32-bit or 64-bit if I installed 64bit SQL2000 E
E on 32-bit Windows 2003 Enterprise server?Please do not multi-post. You cannot install a 64-bit app on a 32-bit
server.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Dipesh" <anonymous@.discussions.microsoft.com> wrote in message
news:B3C23FBD-BE47-4F5E-B464-905A1B94000A@.microsoft.com...
Will my SQL server work like 32-bit or 64-bit if I installed 64bit SQL2000
EE on 32-bit Windows 2003 Enterprise server?|||It will work like a rock. It will sit there and do nothing.
To run 64-bit, you need 64-bit hardware, 64-bit OS, and 64-bit applications.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Dipesh" <anonymous@.discussions.microsoft.com> wrote in message
news:B3C23FBD-BE47-4F5E-B464-905A1B94000A@.microsoft.com...
> Will my SQL server work like 32-bit or 64-bit if I installed 64bit SQL2000
EE on 32-bit Windows 2003 Enterprise server?
>

Tuesday, March 27, 2012

A feature available in oracle, is it available in sql server?

Tuesday, March 20, 2012

a bug in Enterprise Manager ?

a bug in Enterprise Manager ?

a bug in Enterprise Manager ?

a better Enterprise Manager plz

a better Enterprise Manager plz

a better Enterprise Manager plz

Monday, March 19, 2012

8GB RAM in SQL Server

8GB memory installation

Sunday, March 11, 2012

'8007007F' error

'8007007F' error

8000 char Row limit

8000 char Row limit

8000 char Row limit

8 GB of RAM installed

8 GB of RAM installed

8 GB of RAM

8 GB of RAM

8 GB of RAM

Tuesday, March 6, 2012

64-bit SQL2000 on 32-bit OS

3G ram for SQL server

Blog Archive

About Me