New System.OutOfMemoryException on RTM release

Last week I removed the CTP version of SQL Server 2005 and installed the RTM
SQL Server 2005 Developer from the MSDN downloads. In doing some baseline
testing, I discovered that a trivial query that had been working correctly is
now generating:
"An error occurred while executing batch. Error message is: Exception of
type 'System.OutOfMemoryException' was thrown."
I installed fresh Microsoft Windows Server 2003 Standard + SP + critical
updates.
I installed fresh SQL Server 2005 Developer RTM.
The error still occurs. The query is "select <column> from <table>", where
column is a date_time field. Number of rows in <table> is about 42 million
... a mediums-sized table for our customers.
The machine hardware has not changed. It is a development box with a 3.0GHz
hyperthreaded P4 and 2GB of RAM. Something like 200GB of disk available.
Current space allocated to the database is 2X data size and 2x log size with
autogrowth at 100MB on each.
Only "unusual" thing about the box is that it has an Infineon Trusted
Platform Module installed. Device manager says that its active and working
correctly. In the My Computer -> Properties dialog box on the General tab, in
the Computer: section, below the lines that give the processor and RAM
information, appears the text "Physical Address Extension". I've never seen
this before and I don't know if it's related to the TPM or to the problem for
that matter.
This is looking like a client-side issue. It occurs when going against a
duplicate database an another server (SQL Server 2000) as well. When I
switched output from grid to text it still errored out, but the the error is
"Could not replace text."
The same query in the SQL Server 2000 QA executes will no problem, returned
the expected 42 million+ rows.
"ScottL" wrote:

> Last week I removed the CTP version of SQL Server 2005 and installed the RTM
> SQL Server 2005 Developer from the MSDN downloads. In doing some baseline
> testing, I discovered that a trivial query that had been working correctly is
> now generating:
> "An error occurred while executing batch. Error message is: Exception of
> type 'System.OutOfMemoryException' was thrown."
> I installed fresh Microsoft Windows Server 2003 Standard + SP + critical
> updates.
> I installed fresh SQL Server 2005 Developer RTM.
> The error still occurs. The query is "select <column> from <table>", where
> column is a date_time field. Number of rows in <table> is about 42 million
> ... a mediums-sized table for our customers.
> The machine hardware has not changed. It is a development box with a 3.0GHz
> hyperthreaded P4 and 2GB of RAM. Something like 200GB of disk available.
> Current space allocated to the database is 2X data size and 2x log size with
> autogrowth at 100MB on each.
> Only "unusual" thing about the box is that it has an Infineon Trusted
> Platform Module installed. Device manager says that its active and working
> correctly. In the My Computer -> Properties dialog box on the General tab, in
> the Computer: section, below the lines that give the processor and RAM
> information, appears the text "Physical Address Extension". I've never seen
> this before and I don't know if it's related to the TPM or to the problem for
> that matter.
>
>
|||Hi Scott,
Welcome to use MSDN Managed Newsgroup!
Thanks so much for your detailed information. From your descriptions, I
understood your query via SQL Server 2005 RTM will report the error message
"An error occurred while executing batch. Error message is: Exception of
type 'System.OutOfMemoryException' was thrown". If I have misunderstood
your concern, please feel free to point it out.
Based on my knowledge, since SQL Server Management Studio was built via
.NET technology. The limitation of System.Data.DataRows might be the root
cause for this error message. When total memory footprint was used up by 42
million rows, Management Studio will report System.OutOfMemoryException.
For now, answer/perform the steps below and let me know the result.
1. If you use SELECT statement to select other tables in AdventureWorks,
will it reproduce this behavior? For example
use AdventureWorks
go
SELECT * FROM HumanResources.Employee
go
2. If you change the SELECT statement to be SELECT TOP 100 <column> from
<table>, will you get the result as expected?
3. If you connect SQL Server via SQLCMD instead of SQL Server Management
Studio, will this SELECT statement report the error message?
4. In the SQL Server Management Studio, click menu Query -> Query
Options...
Make sure everything was set to Default and then have a test again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael, thanks for the response. Here are the additional results you
requested:
1. Sorry, AdventureWorks is not loaded, so I instead executed the same query
against a summary table with 2.1 million rows. Result: completed OK. Then I
executed the same query against a detail table with 6.3 million rows. Result:
completed OK.
2. Experimenting with TOP shows that 100 records = OK, 40 million = error,
20 million = OK, 30 million = OK, 35 million = error. So on this system with
it's current processes, it begins to error out between 30 and 35 million rows.
3. I am assuming that you mean to use SQLCMD from the command line so that
it uses OleDB, not SQLCMD Mode in Management Studio. I ran the following
query from a command shell window:
sqlcmd -S <server name> -U sa -P <password> -d <db name> -q "select <column>
from <table>"
Result: Completed OK - 42.x million rows returned.
Actually, I went ahead and ran the query using SQLCMD Mode in Management
Studio as well (so as to try SQLCMD using SqlClient as a provider).
Result: same error, System.OutOfMemoryException
4. I selected Query --> Query Options and on the Query Options dialog
selected the button Reset to Default for each of the property pages. Clicked
OK to close dialog and reran the original query.
Result: same error, System.OutOfMemoryException

> .NET technology. The limitation of System.Data.DataRows might be the root
> cause for this error message. When total memory footprint was used up by 42
Note that it also errors when output is in Text mode. The error message is
"An error occurred while executing batch. Error message is: Couldn't replace
text" I repeated the TOP experiments (#2) in text mode. The results were: 100
rows = OK, 40 million = error, 20 million = error, 10 million = OK, 15
million = error.
Please advise. I know that this is kind of a far-out case, but this is
exactly the kind of thing that some of our customers will do and when it no
longer works with SQL Server 2005, as MS knows, we ISVs will be the
customers' first support call. :-)
Thanks, Scott
"Michael Cheng [MSFT]" wrote:

> Hi Scott,
> Welcome to use MSDN Managed Newsgroup!
> Thanks so much for your detailed information. From your descriptions, I
> understood your query via SQL Server 2005 RTM will report the error message
> "An error occurred while executing batch. Error message is: Exception of
> type 'System.OutOfMemoryException' was thrown". If I have misunderstood
> your concern, please feel free to point it out.
> Based on my knowledge, since SQL Server Management Studio was built via
> .NET technology. The limitation of System.Data.DataRows might be the root
> cause for this error message. When total memory footprint was used up by 42
> million rows, Management Studio will report System.OutOfMemoryException.
> For now, answer/perform the steps below and let me know the result.
> 1. If you use SELECT statement to select other tables in AdventureWorks,
> will it reproduce this behavior? For example
> use AdventureWorks
> go
> SELECT * FROM HumanResources.Employee
> go
> 2. If you change the SELECT statement to be SELECT TOP 100 <column> from
> <table>, will you get the result as expected?
> 3. If you connect SQL Server via SQLCMD instead of SQL Server Management
> Studio, will this SELECT statement report the error message?
> 4. In the SQL Server Management Studio, click menu Query -> Query
> Options...
> Make sure everything was set to Default and then have a test again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
|||Hi Scott,
Thanks for your testing and prompt update.
I believe too much results bring up the error message:
System.OutOfMemoryException. I am afriad this is a by design "feature" for
SQL Server Management Studio 2005 and we do not have a better workaround
except not using SSMS 2005.
You may also submit your feedback to the site below
http://lab.msdn.microsoft.com/produc...k/default.aspx
If this is urgent, you may open a Support incident with Microsoft Customer
Service and Support (CSS) so that a dedicated Support Professional can work
with you in a more timely and efficient manner. If you need any help in
this regard, please let me know.
Please be advised that contacting phone support will be a charged call.
However, if you are simply requesting a hotfix be sent to you and no other
support then charges are usually refunded or waived.
For a complete list of Microsoft Customer Service and Support phone
numbers, please go to the following address on the World Wide Web:
<http://support.microsoft.com/directory/overview.asp>
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

New System.OutOfMemoryException on RTM release

Last week I removed the CTP version of SQL Server 2005 and installed the RTM
SQL Server 2005 Developer from the MSDN downloads. In doing some baseline
testing, I discovered that a trivial query that had been working correctly is
now generating:
"An error occurred while executing batch. Error message is: Exception of
type 'System.OutOfMemoryException' was thrown."
I installed fresh Microsoft Windows Server 2003 Standard + SP + critical
updates.
I installed fresh SQL Server 2005 Developer RTM.
The error still occurs. The query is "select <column> from <table>", where
column is a date_time field. Number of rows in <table> is about 42 million
... a mediums-sized table for our customers.
The machine hardware has not changed. It is a development box with a 3.0GHz
hyperthreaded P4 and 2GB of RAM. Something like 200GB of disk available.
Current space allocated to the database is 2X data size and 2x log size with
autogrowth at 100MB on each.
Only "unusual" thing about the box is that it has an Infineon Trusted
Platform Module installed. Device manager says that its active and working
correctly. In the My Computer -> Properties dialog box on the General tab, in
the Computer: section, below the lines that give the processor and RAM
information, appears the text "Physical Address Extension". I've never seen
this before and I don't know if it's related to the TPM or to the problem for
that matter.This is looking like a client-side issue. It occurs when going against a
duplicate database an another server (SQL Server 2000) as well. When I
switched output from grid to text it still errored out, but the the error is
"Could not replace text."
The same query in the SQL Server 2000 QA executes will no problem, returned
the expected 42 million+ rows.
"ScottL" wrote:
> Last week I removed the CTP version of SQL Server 2005 and installed the RTM
> SQL Server 2005 Developer from the MSDN downloads. In doing some baseline
> testing, I discovered that a trivial query that had been working correctly is
> now generating:
> "An error occurred while executing batch. Error message is: Exception of
> type 'System.OutOfMemoryException' was thrown."
> I installed fresh Microsoft Windows Server 2003 Standard + SP + critical
> updates.
> I installed fresh SQL Server 2005 Developer RTM.
> The error still occurs. The query is "select <column> from <table>", where
> column is a date_time field. Number of rows in <table> is about 42 million
> ... a mediums-sized table for our customers.
> The machine hardware has not changed. It is a development box with a 3.0GHz
> hyperthreaded P4 and 2GB of RAM. Something like 200GB of disk available.
> Current space allocated to the database is 2X data size and 2x log size with
> autogrowth at 100MB on each.
> Only "unusual" thing about the box is that it has an Infineon Trusted
> Platform Module installed. Device manager says that its active and working
> correctly. In the My Computer -> Properties dialog box on the General tab, in
> the Computer: section, below the lines that give the processor and RAM
> information, appears the text "Physical Address Extension". I've never seen
> this before and I don't know if it's related to the TPM or to the problem for
> that matter.
>
>|||Hi Scott,
Welcome to use MSDN Managed Newsgroup!
Thanks so much for your detailed information. From your descriptions, I
understood your query via SQL Server 2005 RTM will report the error message
"An error occurred while executing batch. Error message is: Exception of
type 'System.OutOfMemoryException' was thrown". If I have misunderstood
your concern, please feel free to point it out.
Based on my knowledge, since SQL Server Management Studio was built via|||Hi Michael, thanks for the response. Here are the additional results you
requested:
1. Sorry, AdventureWorks is not loaded, so I instead executed the same query
against a summary table with 2.1 million rows. Result: completed OK. Then I
executed the same query against a detail table with 6.3 million rows. Result:
completed OK.
2. Experimenting with TOP shows that 100 records = OK, 40 million = error,
20 million = OK, 30 million = OK, 35 million = error. So on this system with
it's current processes, it begins to error out between 30 and 35 million rows.
3. I am assuming that you mean to use SQLCMD from the command line so that
it uses OleDB, not SQLCMD Mode in Management Studio. I ran the following
query from a command shell window:
sqlcmd -S <server name> -U sa -P <password> -d <db name> -q "select <column>
from <table>"
Result: Completed OK - 42.x million rows returned.
Actually, I went ahead and ran the query using SQLCMD Mode in Management
Studio as well (so as to try SQLCMD using SqlClient as a provider).
Result: same error, System.OutOfMemoryException
4. I selected Query --> Query Options and on the Query Options dialog
selected the button Reset to Default for each of the property pages. Clicked
OK to close dialog and reran the original query.
Result: same error, System.OutOfMemoryException
> .NET technology. The limitation of System.Data.DataRows might be the root
> cause for this error message. When total memory footprint was used up by 42
Note that it also errors when output is in Text mode. The error message is
"An error occurred while executing batch. Error message is: Couldn't replace
text" I repeated the TOP experiments (#2) in text mode. The results were: 100
rows = OK, 40 million = error, 20 million = error, 10 million = OK, 15
million = error.
Please advise. I know that this is kind of a far-out case, but this is
exactly the kind of thing that some of our customers will do and when it no
longer works with SQL Server 2005, as MS knows, we ISVs will be the
customers' first support call. :-)
Thanks, Scott
"Michael Cheng [MSFT]" wrote:
> Hi Scott,
> Welcome to use MSDN Managed Newsgroup!
> Thanks so much for your detailed information. From your descriptions, I
> understood your query via SQL Server 2005 RTM will report the error message
> "An error occurred while executing batch. Error message is: Exception of
> type 'System.OutOfMemoryException' was thrown". If I have misunderstood
> your concern, please feel free to point it out.
> Based on my knowledge, since SQL Server Management Studio was built via
> .NET technology. The limitation of System.Data.DataRows might be the root
> cause for this error message. When total memory footprint was used up by 42
> million rows, Management Studio will report System.OutOfMemoryException.
> For now, answer/perform the steps below and let me know the result.
> 1. If you use SELECT statement to select other tables in AdventureWorks,
> will it reproduce this behavior? For example
> use AdventureWorks
> go
> SELECT * FROM HumanResources.Employee
> go
> 2. If you change the SELECT statement to be SELECT TOP 100 <column> from
> <table>, will you get the result as expected?
> 3. If you connect SQL Server via SQLCMD instead of SQL Server Management
> Studio, will this SELECT statement report the error message?
> 4. In the SQL Server Management Studio, click menu Query -> Query
> Options...
> Make sure everything was set to Default and then have a test again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>|||Hi Scott,
Thanks for your testing and prompt update.
I believe too much results bring up the error message:
System.OutOfMemoryException. I am afriad this is a by design "feature" for
SQL Server Management Studio 2005 and we do not have a better workaround
except not using SSMS 2005.
You may also submit your feedback to the site below
http://lab.msdn.microsoft.com/productfeedback/default.aspx
If this is urgent, you may open a Support incident with Microsoft Customer
Service and Support (CSS) so that a dedicated Support Professional can work
with you in a more timely and efficient manner. If you need any help in
this regard, please let me know.
Please be advised that contacting phone support will be a charged call.
However, if you are simply requesting a hotfix be sent to you and no other
support then charges are usually refunded or waived.
For a complete list of Microsoft Customer Service and Support phone
numbers, please go to the following address on the World Wide Web:
<http://support.microsoft.com/directory/overview.asp>
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

New System.OutOfMemoryException on RTM release

Last week I removed the CTP version of SQL Server 2005 and installed the RTM
SQL Server 2005 Developer from the MSDN downloads. In doing some baseline
testing, I discovered that a trivial query that had been working correctly i
s
now generating:
"An error occurred while executing batch. Error message is: Exception of
type 'System.OutOfMemoryException' was thrown."
I installed fresh Microsoft Windows Server 2003 Standard + SP + critical
updates.
I installed fresh SQL Server 2005 Developer RTM.
The error still occurs. The query is "select <column> from <table>", where
column is a date_time field. Number of rows in <table> is about 42 million
... a mediums-sized table for our customers.
The machine hardware has not changed. It is a development box with a 3.0GHz
hyperthreaded P4 and 2GB of RAM. Something like 200GB of disk available.
Current space allocated to the database is 2X data size and 2x log size with
autogrowth at 100MB on each.
Only "unusual" thing about the box is that it has an Infineon Trusted
Platform Module installed. Device manager says that its active and working
correctly. In the My Computer -> Properties dialog box on the General tab, i
n
the Computer: section, below the lines that give the processor and RAM
information, appears the text "Physical Address Extension". I've never seen
this before and I don't know if it's related to the TPM or to the problem fo
r
that matter.This is looking like a client-side issue. It occurs when going against a
duplicate database an another server (SQL Server 2000) as well. When I
switched output from grid to text it still errored out, but the the error is
"Could not replace text."
The same query in the SQL Server 2000 QA executes will no problem, returned
the expected 42 million+ rows.
"ScottL" wrote:

> Last week I removed the CTP version of SQL Server 2005 and installed the R
TM
> SQL Server 2005 Developer from the MSDN downloads. In doing some baseline
> testing, I discovered that a trivial query that had been working correctly
is
> now generating:
> "An error occurred while executing batch. Error message is: Exception of
> type 'System.OutOfMemoryException' was thrown."
> I installed fresh Microsoft Windows Server 2003 Standard + SP + critical
> updates.
> I installed fresh SQL Server 2005 Developer RTM.
> The error still occurs. The query is "select <column> from <table>", where
> column is a date_time field. Number of rows in <table> is about 42 million
> ... a mediums-sized table for our customers.
> The machine hardware has not changed. It is a development box with a 3.0GH
z
> hyperthreaded P4 and 2GB of RAM. Something like 200GB of disk available.
> Current space allocated to the database is 2X data size and 2x log size wi
th
> autogrowth at 100MB on each.
> Only "unusual" thing about the box is that it has an Infineon Trusted
> Platform Module installed. Device manager says that its active and working
> correctly. In the My Computer -> Properties dialog box on the General tab,
in
> the Computer: section, below the lines that give the processor and RAM
> information, appears the text "Physical Address Extension". I've never see
n
> this before and I don't know if it's related to the TPM or to the problem
for
> that matter.
>
>|||Hi Scott,
Welcome to use MSDN Managed Newsgroup!
Thanks so much for your detailed information. From your descriptions, I
understood your query via SQL Server 2005 RTM will report the error message
"An error occurred while executing batch. Error message is: Exception of
type 'System.OutOfMemoryException' was thrown". If I have misunderstood
your concern, please feel free to point it out.
Based on my knowledge, since SQL Server Management Studio was built via
.NET technology. The limitation of System.Data.DataRows might be the root
cause for this error message. When total memory footprint was used up by 42
million rows, Management Studio will report System.OutOfMemoryException.
For now, answer/perform the steps below and let me know the result.
1. If you use SELECT statement to select other tables in AdventureWorks,
will it reproduce this behavior? For example
use AdventureWorks
go
SELECT * FROM HumanResources.Employee
go
2. If you change the SELECT statement to be SELECT TOP 100 <column> from
<table>, will you get the result as expected?
3. If you connect SQL Server via SQLCMD instead of SQL Server Management
Studio, will this SELECT statement report the error message?
4. In the SQL Server Management Studio, click menu Query -> Query
Options...
Make sure everything was set to Default and then have a test again.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael, thanks for the response. Here are the additional results you
requested:
1. Sorry, AdventureWorks is not loaded, so I instead executed the same query
against a summary table with 2.1 million rows. Result: completed OK. Then I
executed the same query against a detail table with 6.3 million rows. Result
:
completed OK.
2. Experimenting with TOP shows that 100 records = OK, 40 million = error,
20 million = OK, 30 million = OK, 35 million = error. So on this system with
it's current processes, it begins to error out between 30 and 35 million row
s.
3. I am assuming that you mean to use SQLCMD from the command line so that
it uses OleDB, not SQLCMD Mode in Management Studio. I ran the following
query from a command shell window:
sqlcmd -S <server name> -U sa -P <password> -d <db name> -q "select <column>
from <table>"
Result: Completed OK - 42.x million rows returned.
Actually, I went ahead and ran the query using SQLCMD Mode in Management
Studio as well (so as to try SQLCMD using SqlClient as a provider).
Result: same error, System.OutOfMemoryException
4. I selected Query --> Query Options and on the Query Options dialog
selected the button Reset to Default for each of the property pages. Clicked
OK to close dialog and reran the original query.
Result: same error, System.OutOfMemoryException

> .NET technology. The limitation of System.Data.DataRows might be the root
> cause for this error message. When total memory footprint was used up by 42[/vbcol
]
Note that it also errors when output is in Text mode. The error message is
"An error occurred while executing batch. Error message is: Couldn't replace
text" I repeated the TOP experiments (#2) in text mode. The results were: 10
0
rows = OK, 40 million = error, 20 million = error, 10 million = OK, 15
million = error.
Please advise. I know that this is kind of a far-out case, but this is
exactly the kind of thing that some of our customers will do and when it no
longer works with SQL Server 2005, as MS knows, we ISVs will be the
customers' first support call. :-)
Thanks, Scott
"Michael Cheng [MSFT]" wrote:
[vbcol=seagreen]
> Hi Scott,
> Welcome to use MSDN Managed Newsgroup!
> Thanks so much for your detailed information. From your descriptions, I
> understood your query via SQL Server 2005 RTM will report the error messag
e
> "An error occurred while executing batch. Error message is: Exception of
> type 'System.OutOfMemoryException' was thrown". If I have misunderstood
> your concern, please feel free to point it out.
> Based on my knowledge, since SQL Server Management Studio was built via
> .NET technology. The limitation of System.Data.DataRows might be the root
> cause for this error message. When total memory footprint was used up by 4
2
> million rows, Management Studio will report System.OutOfMemoryException.
> For now, answer/perform the steps below and let me know the result.
> 1. If you use SELECT statement to select other tables in AdventureWorks,
> will it reproduce this behavior? For example
> use AdventureWorks
> go
> SELECT * FROM HumanResources.Employee
> go
> 2. If you change the SELECT statement to be SELECT TOP 100 <column> from
> <table>, will you get the result as expected?
> 3. If you connect SQL Server via SQLCMD instead of SQL Server Management
> Studio, will this SELECT statement report the error message?
> 4. In the SQL Server Management Studio, click menu Query -> Query
> Options...
> Make sure everything was set to Default and then have a test again.
> Thank you for your patience and cooperation. If you have any questions or
> concerns, don't hesitate to let me know. We are always here to be of
> assistance!
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>
>|||Hi Scott,
Thanks for your testing and prompt update.
I believe too much results bring up the error message:
System.OutOfMemoryException. I am afriad this is a by design "feature" for
SQL Server Management Studio 2005 and we do not have a better workaround
except not using SSMS 2005.
You may also submit your feedback to the site below
http://lab.msdn.microsoft.com/produ...ck/default.aspx
If this is urgent, you may open a Support incident with Microsoft Customer
Service and Support (CSS) so that a dedicated Support Professional can work
with you in a more timely and efficient manner. If you need any help in
this regard, please let me know.
Please be advised that contacting phone support will be a charged call.
However, if you are simply requesting a hotfix be sent to you and no other
support then charges are usually refunded or waived.
For a complete list of Microsoft Customer Service and Support phone
numbers, please go to the following address on the World Wide Web:
<http://support.microsoft.com/directory/overview.asp>
If you are outside the US please see http://support.microsoft.com for
regional support phone numbers.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.sql

New SQL2005 SP2

Hi,
Bink is saying there is a new version of SP2 http://bink.nu/Article9653.bink
The download site now shows version 9.00.3042.01 dated 3/5/2007. It sounds
like this version fixes the fact that maintenance plan cleanup tasks now
change from days to hours. This change has been talked about here before.
Any one having any newer information on the change?
Thanks
ChrisMicrosoft SQL Server 2005 Service Pack 2 issue: Cleanup tasks run at
different intervals than intended
http://support.microsoft.com/kb/933508
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:O6Nhfw$XHHA.1220@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Bink is saying there is a new version of SP2
> http://bink.nu/Article9653.bink The download site now shows version
> 9.00.3042.01 dated 3/5/2007. It sounds like this version fixes the fact
> that maintenance plan cleanup tasks now change from days to hours. This
> change has been talked about here before.
> Any one having any newer information on the change?
> Thanks
> Chris
>

New SQL2005 SP2

Hi,
Bink is saying there is a new version of SP2 http://bink.nu/Article9653.bink
The download site now shows version 9.00.3042.01 dated 3/5/2007. It sounds
like this version fixes the fact that maintenance plan cleanup tasks now
change from days to hours. This change has been talked about here before.
Any one having any newer information on the change?
Thanks
Chris
Microsoft SQL Server 2005 Service Pack 2 issue: Cleanup tasks run at
different intervals than intended
http://support.microsoft.com/kb/933508
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:O6Nhfw$XHHA.1220@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Bink is saying there is a new version of SP2
> http://bink.nu/Article9653.bink The download site now shows version
> 9.00.3042.01 dated 3/5/2007. It sounds like this version fixes the fact
> that maintenance plan cleanup tasks now change from days to hours. This
> change has been talked about here before.
> Any one having any newer information on the change?
> Thanks
> Chris
>

New SQL2005 SP2

Hi,
Bink is saying there is a new version of SP2 http://bink.nu/Article9653.bink
The download site now shows version 9.00.3042.01 dated 3/5/2007. It sounds
like this version fixes the fact that maintenance plan cleanup tasks now
change from days to hours. This change has been talked about here before.
Any one having any newer information on the change?
Thanks
ChrisMicrosoft SQL Server 2005 Service Pack 2 issue: Cleanup tasks run at
different intervals than intended
http://support.microsoft.com/kb/933508
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:O6Nhfw$XHHA.1220@.TK2MSFTNGP03.phx.gbl...
> Hi,
> Bink is saying there is a new version of SP2
> http://bink.nu/Article9653.bink The download site now shows version
> 9.00.3042.01 dated 3/5/2007. It sounds like this version fixes the fact
> that maintenance plan cleanup tasks now change from days to hours. This
> change has been talked about here before.
> Any one having any newer information on the change?
> Thanks
> Chris
>sql

New SQL Server tool

Quest Software has released a SQL Server version of its highly popular
Oracle tool - TOAD. It is freeware! You can see more about it at
http://www.toadsoft.com/toadss.html and download it at
http://www.toadsoft.com/toad_ss.zip.Thats Cool, I have been using toad for a while on Oracle, and I am glad you
have a sql version now, I will download and evaluate it straight away

--
Dandy Weyn, Belgium
MCSE, MCSA, MCDBA, MCT

http://www.dandyman.net

Check my SQL Server resource pages (currently under construction)
http://www.dandyman.net/sql

"Bert Scalzo" <bert.scalzo@.comcast.net> wrote in message
news:7e3dac68.0402140948.30189336@.posting.google.c om...
> Quest Software has released a SQL Server version of its highly popular
> Oracle tool - TOAD. It is freeware! You can see more about it at
> http://www.toadsoft.com/toadss.html and download it at
> http://www.toadsoft.com/toad_ss.zip.|||Looked at it and it does absolutely nothing that QA does not do. You cannot
test procedures/run scripts. Free and does nothing. Sorry Bert, you know
in your heart that it cannot come close to SQL-Programmer.

Lloyd Sheen

"Dandy WEYN" <no_spam_info@.dandyman.net> wrote in message
news:402e7117$0$13251$ba620e4c@.news.skynet.be...
> Thats Cool, I have been using toad for a while on Oracle, and I am glad
you
> have a sql version now, I will download and evaluate it straight away
>
> --
> Dandy Weyn, Belgium
> MCSE, MCSA, MCDBA, MCT
> http://www.dandyman.net
> Check my SQL Server resource pages (currently under construction)
> http://www.dandyman.net/sql
>
> "Bert Scalzo" <bert.scalzo@.comcast.net> wrote in message
> news:7e3dac68.0402140948.30189336@.posting.google.c om...
> > Quest Software has released a SQL Server version of its highly popular
> > Oracle tool - TOAD. It is freeware! You can see more about it at
> > http://www.toadsoft.com/toadss.html and download it at
> > http://www.toadsoft.com/toad_ss.zip.

New SQL Server tool

Quest Software has released a SQL Server version of its highly popular
Oracle tool - TOAD. It is freeware! You can see more about it at
http://www.toadsoft.com/toadss.html and download it at
http://www.toadsoft.com/toad_ss.zip.Thats Cool, I have been using toad for a while on Oracle, and I am glad you
have a sql version now, I will download and evaluate it straight away
Dandy Weyn, Belgium
MCSE, MCSA, MCDBA, MCT
http://www.dandyman.net
Check my SQL Server resource pages (currently under construction)
http://www.dandyman.net/sql
"Bert Scalzo" <bert.scalzo@.comcast.net> wrote in message
news:7e3dac68.0402140948.30189336@.posting.google.com...
> Quest Software has released a SQL Server version of its highly popular
> Oracle tool - TOAD. It is freeware! You can see more about it at
> http://www.toadsoft.com/toadss.html and download it at
> http://www.toadsoft.com/toad_ss.zip.|||Looked at it and it does absolutely nothing that QA does not do. You cannot
test procedures/run scripts. Free and does nothing. Sorry Bert, you know
in your heart that it cannot come close to SQL-Programmer.
Lloyd Sheen
"Dandy WEYN" <no_spam_info@.dandyman.net> wrote in message
news:402e7117$0$13251$ba620e4c@.news.skynet.be...
> Thats Cool, I have been using toad for a while on Oracle, and I am glad
you
> have a sql version now, I will download and evaluate it straight away
>
> --
> Dandy Weyn, Belgium
> MCSE, MCSA, MCDBA, MCT
> http://www.dandyman.net
> Check my SQL Server resource pages (currently under construction)
> http://www.dandyman.net/sql
>
> "Bert Scalzo" <bert.scalzo@.comcast.net> wrote in message
> news:7e3dac68.0402140948.30189336@.posting.google.com...
>sql

New SQL Server tool

Quest Software has released a SQL Server version of its highly popular Oracle tool - TOAD. It is f
reeware! You can see more about it at http://www.toadsoft.com/toadss.html and donwload
it at http://www.toadsoft.com/toad_ss.zip.This is not a Quest Software tool from what I can tell.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"bscalzo" <anonymous@.discussions.microsoft.com> wrote in message
news:1C861ACD-D17B-4A71-86D3-D0384C5C117A@.microsoft.com...
> Quest Software has released a SQL Server version of its highly popular
Oracle tool - TOAD. It is freeware! You can see more about it at
http://www.toadsoft.com/toadss.html and donwload it at
http://www.toadsoft.com/toad_ss.zip.|||Quest Software owns TOAD and TOADSOFT web site. The developers just find it
easier to post things using this site rather than the official Quest web sit
e. But it is owned and managed by Quest - and it is Quest employees who buil
t this product. I know, bec
ause I'm on the team ...

New SQL Server tool

Quest Software has released a SQL Server version of its highly popular Oracle tool - TOAD. It is freeware! You can see more about it at http://www.toadsoft.com/toadss.html and donwload it at http://www.toadsoft.com/toad_ss.zip.This is not a Quest Software tool from what I can tell.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"bscalzo" <anonymous@.discussions.microsoft.com> wrote in message
news:1C861ACD-D17B-4A71-86D3-D0384C5C117A@.microsoft.com...
> Quest Software has released a SQL Server version of its highly popular
Oracle tool - TOAD. It is freeware! You can see more about it at
http://www.toadsoft.com/toadss.html and donwload it at
http://www.toadsoft.com/toad_ss.zip.|||Quest Software owns TOAD and TOADSOFT web site. The developers just find it easier to post things using this site rather than the official Quest web site. But it is owned and managed by Quest - and it is Quest employees who built this product. I know, because I'm on the team ...

New SQL Server tool

Quest Software has released a SQL Server version of its highly popular
Oracle tool - TOAD. It is freeware! You can see more about it at
http://www.toadsoft.com/toadss.html and download it at
http://www.toadsoft.com/toad_ss.zip.Thats Cool, I have been using toad for a while on Oracle, and I am glad you
have a sql version now, I will download and evaluate it straight away
Dandy Weyn, Belgium
MCSE, MCSA, MCDBA, MCT
http://www.dandyman.net
Check my SQL Server resource pages (currently under construction)
http://www.dandyman.net/sql
"Bert Scalzo" <bert.scalzo@.comcast.net> wrote in message
news:7e3dac68.0402140948.30189336@.posting.google.com...
> Quest Software has released a SQL Server version of its highly popular
> Oracle tool - TOAD. It is freeware! You can see more about it at
> http://www.toadsoft.com/toadss.html and download it at
> http://www.toadsoft.com/toad_ss.zip.|||Looked at it and it does absolutely nothing that QA does not do. You cannot
test procedures/run scripts. Free and does nothing. Sorry Bert, you know
in your heart that it cannot come close to SQL-Programmer.
Lloyd Sheen
"Dandy WEYN" <no_spam_info@.dandyman.net> wrote in message
news:402e7117$0$13251$ba620e4c@.news.skynet.be...
> Thats Cool, I have been using toad for a while on Oracle, and I am glad
you
> have a sql version now, I will download and evaluate it straight away
>
> --
> Dandy Weyn, Belgium
> MCSE, MCSA, MCDBA, MCT
> http://www.dandyman.net
> Check my SQL Server resource pages (currently under construction)
> http://www.dandyman.net/sql
>
> "Bert Scalzo" <bert.scalzo@.comcast.net> wrote in message
> news:7e3dac68.0402140948.30189336@.posting.google.com...
> > Quest Software has released a SQL Server version of its highly popular
> > Oracle tool - TOAD. It is freeware! You can see more about it at
> > http://www.toadsoft.com/toadss.html and download it at
> > http://www.toadsoft.com/toad_ss.zip.
>

new server to install, Win 2003 x64 will be used... which SQL Version?

Hi,
I have to install a new server and I am a little confused about working
combinations between 30bits, x64 and IA64...
My server use intel Xeon processors with EMT64.
So I want to install Windows 2003 x64 Ent.
but which version of SQL Server can I install?
the 64bits?
32bits + SP4 (Sql2k64sp4.exe)?
Also I have to install Reporting Services, Analysis Services & Sharepoint.
Does everything works on Win x64?
I'm using SQL Server 2000 enterprise edition.
thanks for your answer.
Jerome.
You need the SQL Server 2000 (64-bit) edition.
http://www.microsoft.com/sql/64bit/default.mspx
--Brian
(Please reply to the newsgroups only.)
"Jj" <willgart_A_@.hotmail_A_.com> wrote in message
news:e%2313sduuFHA.3764@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have to install a new server and I am a little confused about working
> combinations between 30bits, x64 and IA64...
> My server use intel Xeon processors with EMT64.
> So I want to install Windows 2003 x64 Ent.
> but which version of SQL Server can I install?
> the 64bits?
> 32bits + SP4 (Sql2k64sp4.exe)?
> Also I have to install Reporting Services, Analysis Services & Sharepoint.
> Does everything works on Win x64?
> I'm using SQL Server 2000 enterprise edition.
> thanks for your answer.
> Jerome.
>
|||what you really need; you need to wait for sql 2005 and it'll be a LOT
better
|||unfortunatly its an hardware migration process.
we change an old server to a new one
so we can't deploy 2005.
but I have to insure that the 64bits edition (of SQL, RS, AS) works
correctly on Win 2003 x64.
if there is any issue or compatibility problem, I'll use the 32bit edition.
<dbahooker@.hotmail.com> wrote in message
news:1126900439.484602.107740@.g44g2000cwa.googlegr oups.com...
> what you really need; you need to wait for sql 2005 and it'll be a LOT
> better
>
|||Hi
No, 32 Bit plus SP4.
SQL Server 2000 64 Bit is complied for the Intel Itanium Processor and will
not run on Xeons.
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/
"Brian Lawton" <brian.k.lawton@.redtailcreek.com> wrote in message
news:%23QD6nsuuFHA.1472@.TK2MSFTNGP15.phx.gbl...
> You need the SQL Server 2000 (64-bit) edition.
> http://www.microsoft.com/sql/64bit/default.mspx
> --
> --Brian
> (Please reply to the newsgroups only.)
>
> "Jj" <willgart_A_@.hotmail_A_.com> wrote in message
> news:e%2313sduuFHA.3764@.TK2MSFTNGP09.phx.gbl...
>
|||If you are going to install the 64-bit version of the Win2K3 make sure:
1) you install SP1 of Win2K3 x64 -- and
2) you use SP4
Both are required to run AS2K on x64 hardware with a 64-bit OS.
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jj" <willgart_A_@.hotmail_A_.com> wrote in message
news:ONOy27vuFHA.2072@.TK2MSFTNGP14.phx.gbl...
> unfortunatly its an hardware migration process.
> we change an old server to a new one
> so we can't deploy 2005.
> but I have to insure that the 64bits edition (of SQL, RS, AS) works
> correctly on Win 2003 x64.
> if there is any issue or compatibility problem, I'll use the 32bit
> edition.
>
> <dbahooker@.hotmail.com> wrote in message
> news:1126900439.484602.107740@.g44g2000cwa.googlegr oups.com...
>
|||Thankls.
I have all of this on my CD Roms...
so finally, there is no issue in mind(?)
"Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message
news:%23ultf2XvFHA.4032@.TK2MSFTNGP15.phx.gbl...
> If you are going to install the 64-bit version of the Win2K3 make sure:
> 1) you install SP1 of Win2K3 x64 -- and
> 2) you use SP4
> Both are required to run AS2K on x64 hardware with a 64-bit OS.
> --
> Dave Wickert [MSFT]
> dwickert@.online.microsoft.com
> Program Manager
> BI Systems Team
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Jj" <willgart_A_@.hotmail_A_.com> wrote in message
> news:ONOy27vuFHA.2072@.TK2MSFTNGP14.phx.gbl...
>
|||I will be deploying this same setup... Windows 2003 Standard x64
Edition running SQL Server 2000 Enterprise Edition SP4. The server I'm
running on has 8GB of RAM. Does anyone know how much RAM SQL Server
will use? My understanding is that this is not an AWE situtation
because the OS can natively address all 8GB of RAM.
Any advice on maximizing this setup would be greatly appreciated.
Thanks.
george sarlas
gsarlas@.yahoo.com
|||> My understanding is that this is not an AWE situtation
> because the OS can natively address all 8GB of RAM.
You are right, SQL Server can access up to 512Gb of RAM, which is the
maximum currently supported by Win2K3 Server.
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell
|||I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
AWE in SQL Server. But to support more than 4GB of RAM, I needed to
install SQL 2000 SP4 and the SP4 AWE Hotfix
(http://support.microsoft.com/default.aspx?kbid=899761).
-george

new server to install, Win 2003 x64 will be used... which SQL Version?

Hi,
I have to install a new server and I am a little confused about working
combinations between 30bits, x64 and IA64...
My server use intel Xeon processors with EMT64.
So I want to install Windows 2003 x64 Ent.
but which version of SQL Server can I install?
the 64bits?
32bits + SP4 (Sql2k64sp4.exe)?
Also I have to install Reporting Services, Analysis Services & Sharepoint.
Does everything works on Win x64?
I'm using SQL Server 2000 enterprise edition.
thanks for your answer.
Jerome.You need the SQL Server 2000 (64-bit) edition.
http://www.microsoft.com/sql/64bit/default.mspx
--
--Brian
(Please reply to the newsgroups only.)
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:e%2313sduuFHA.3764@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have to install a new server and I am a little confused about working
> combinations between 30bits, x64 and IA64...
> My server use intel Xeon processors with EMT64.
> So I want to install Windows 2003 x64 Ent.
> but which version of SQL Server can I install?
> the 64bits?
> 32bits + SP4 (Sql2k64sp4.exe)?
> Also I have to install Reporting Services, Analysis Services & Sharepoint.
> Does everything works on Win x64?
> I'm using SQL Server 2000 enterprise edition.
> thanks for your answer.
> Jerome.
>|||what you really need; you need to wait for sql 2005 and it'll be a LOT
better|||unfortunatly its an hardware migration process.
we change an old server to a new one
so we can't deploy 2005.
but I have to insure that the 64bits edition (of SQL, RS, AS) works
correctly on Win 2003 x64.
if there is any issue or compatibility problem, I'll use the 32bit edition.
<dbahooker@.hotmail.com> wrote in message
news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
> what you really need; you need to wait for sql 2005 and it'll be a LOT
> better
>|||Hi
No, 32 Bit plus SP4.
SQL Server 2000 64 Bit is complied for the Intel Itanium Processor and will
not run on Xeons.
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/
"Brian Lawton" <brian.k.lawton@.redtailcreek.com> wrote in message
news:%23QD6nsuuFHA.1472@.TK2MSFTNGP15.phx.gbl...
> You need the SQL Server 2000 (64-bit) edition.
> http://www.microsoft.com/sql/64bit/default.mspx
> --
> --Brian
> (Please reply to the newsgroups only.)
>
> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
> news:e%2313sduuFHA.3764@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have to install a new server and I am a little confused about working
>> combinations between 30bits, x64 and IA64...
>> My server use intel Xeon processors with EMT64.
>> So I want to install Windows 2003 x64 Ent.
>> but which version of SQL Server can I install?
>> the 64bits?
>> 32bits + SP4 (Sql2k64sp4.exe)?
>> Also I have to install Reporting Services, Analysis Services &
>> Sharepoint.
>> Does everything works on Win x64?
>> I'm using SQL Server 2000 enterprise edition.
>> thanks for your answer.
>> Jerome.
>>
>|||If you are going to install the 64-bit version of the Win2K3 make sure:
1) you install SP1 of Win2K3 x64 -- and
2) you use SP4
Both are required to run AS2K on x64 hardware with a 64-bit OS.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:ONOy27vuFHA.2072@.TK2MSFTNGP14.phx.gbl...
> unfortunatly its an hardware migration process.
> we change an old server to a new one
> so we can't deploy 2005.
> but I have to insure that the 64bits edition (of SQL, RS, AS) works
> correctly on Win 2003 x64.
> if there is any issue or compatibility problem, I'll use the 32bit
> edition.
>
> <dbahooker@.hotmail.com> wrote in message
> news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
>> what you really need; you need to wait for sql 2005 and it'll be a LOT
>> better
>|||Thankls.
I have all of this on my CD Roms...
so finally, there is no issue in mind(?)
"Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message
news:%23ultf2XvFHA.4032@.TK2MSFTNGP15.phx.gbl...
> If you are going to install the 64-bit version of the Win2K3 make sure:
> 1) you install SP1 of Win2K3 x64 -- and
> 2) you use SP4
> Both are required to run AS2K on x64 hardware with a 64-bit OS.
> --
> Dave Wickert [MSFT]
> dwickert@.online.microsoft.com
> Program Manager
> BI Systems Team
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
> news:ONOy27vuFHA.2072@.TK2MSFTNGP14.phx.gbl...
>> unfortunatly its an hardware migration process.
>> we change an old server to a new one
>> so we can't deploy 2005.
>> but I have to insure that the 64bits edition (of SQL, RS, AS) works
>> correctly on Win 2003 x64.
>> if there is any issue or compatibility problem, I'll use the 32bit
>> edition.
>>
>> <dbahooker@.hotmail.com> wrote in message
>> news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
>> what you really need; you need to wait for sql 2005 and it'll be a LOT
>> better
>>
>|||I will be deploying this same setup... Windows 2003 Standard x64
Edition running SQL Server 2000 Enterprise Edition SP4. The server I'm
running on has 8GB of RAM. Does anyone know how much RAM SQL Server
will use? My understanding is that this is not an AWE situtation
because the OS can natively address all 8GB of RAM.
Any advice on maximizing this setup would be greatly appreciated.
Thanks.
--
george sarlas
gsarlas@.yahoo.com|||> My understanding is that this is not an AWE situtation
> because the OS can natively address all 8GB of RAM.
You are right, SQL Server can access up to 512Gb of RAM, which is the
maximum currently supported by Win2K3 Server.
--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell|||I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
AWE in SQL Server. But to support more than 4GB of RAM, I needed to
install SQL 2000 SP4 and the SP4 AWE Hotfix
(http://support.microsoft.com/default.aspx?kbid=899761).
-george|||If you have 64bit SQL 2k you do not need to enable AWE. The knowledge
base article you quote only applies to 32bit SQL 2k. 64bit SQL 2k can
address the maximum amount of memory that Win2k3 can support (which is
512Gb) without turning on any special settings.
--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell
In article <1130256929.245741.68610@.g44g2000cwa.googlegroups.com>,
gsarlas@.yahoo.com says...
> I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
> AWE in SQL Server. But to support more than 4GB of RAM, I needed to
> install SQL 2000 SP4 and the SP4 AWE Hotfix
> (http://support.microsoft.com/default.aspx?kbid=899761).
> -george
>|||Just for clarification...
Unfortunately, SQL Server 2000 64-bit Edition does not work with x64
processors. It only works with the Itanium processor. I am running
32-bit SQL Server 2000 on 64-bit Windows 2003, thus I had to enable
AWE.
-george
Darren Gosbell wrote:
> If you have 64bit SQL 2k you do not need to enable AWE. The knowledge
> base article you quote only applies to 32bit SQL 2k. 64bit SQL 2k can
> address the maximum amount of memory that Win2k3 can support (which is
> 512Gb) without turning on any special settings.
> --
> Regards
> Darren Gosbell [MCSD]
> <dgosbell_at_yahoo_dot_com>
> Blog: http://www.geekswithblogs.net/darrengosbell
> In article <1130256929.245741.68610@.g44g2000cwa.googlegroups.com>,
> gsarlas@.yahoo.com says...
> > I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
> > AWE in SQL Server. But to support more than 4GB of RAM, I needed to
> > install SQL 2000 SP4 and the SP4 AWE Hotfix
> > (http://support.microsoft.com/default.aspx?kbid=899761).
> >
> > -george
> >
> >

new server to install, Win 2003 x64 will be used... which SQL Version?

Hi,
I have to install a new server and I am a little confused about working
combinations between 30bits, x64 and IA64...
My server use intel Xeon processors with EMT64.
So I want to install Windows 2003 x64 Ent.
but which version of SQL Server can I install?
the 64bits?
32bits + SP4 (Sql2k64sp4.exe)?
Also I have to install Reporting Services, Analysis Services & Sharepoint.
Does everything works on Win x64?
I'm using SQL Server 2000 enterprise edition.
thanks for your answer.
Jerome.You need the SQL Server 2000 (64-bit) edition.
http://www.microsoft.com/sql/64bit/default.mspx
--Brian
(Please reply to the newsgroups only.)
"Jj" <willgart_A_@.hotmail_A_.com> wrote in message
news:e%2313sduuFHA.3764@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have to install a new server and I am a little confused about working
> combinations between 30bits, x64 and IA64...
> My server use intel Xeon processors with EMT64.
> So I want to install Windows 2003 x64 Ent.
> but which version of SQL Server can I install?
> the 64bits?
> 32bits + SP4 (Sql2k64sp4.exe)?
> Also I have to install Reporting Services, Analysis Services & Sharepoint.
> Does everything works on Win x64?
> I'm using SQL Server 2000 enterprise edition.
> thanks for your answer.
> Jerome.
>|||what you really need; you need to wait for sql 2005 and it'll be a LOT
better|||unfortunatly its an hardware migration process.
we change an old server to a new one
so we can't deploy 2005.
but I have to insure that the 64bits edition (of SQL, RS, AS) works
correctly on Win 2003 x64.
if there is any issue or compatibility problem, I'll use the 32bit edition.
<dbahooker@.hotmail.com> wrote in message
news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
> what you really need; you need to wait for sql 2005 and it'll be a LOT
> better
>|||Hi
No, 32 Bit plus SP4.
SQL Server 2000 64 Bit is complied for the Intel Itanium Processor and will
not run on Xeons.
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/
"Brian Lawton" <brian.k.lawton@.redtailcreek.com> wrote in message
news:%23QD6nsuuFHA.1472@.TK2MSFTNGP15.phx.gbl...
> You need the SQL Server 2000 (64-bit) edition.
> http://www.microsoft.com/sql/64bit/default.mspx
> --
> --Brian
> (Please reply to the newsgroups only.)
>
> "Jj" <willgart_A_@.hotmail_A_.com> wrote in message
> news:e%2313sduuFHA.3764@.TK2MSFTNGP09.phx.gbl...
>|||If you are going to install the 64-bit version of the Win2K3 make sure:
1) you install SP1 of Win2K3 x64 -- and
2) you use SP4
Both are required to run AS2K on x64 hardware with a 64-bit OS.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jj" <willgart_A_@.hotmail_A_.com> wrote in message
news:ONOy27vuFHA.2072@.TK2MSFTNGP14.phx.gbl...
> unfortunatly its an hardware migration process.
> we change an old server to a new one
> so we can't deploy 2005.
> but I have to insure that the 64bits edition (of SQL, RS, AS) works
> correctly on Win 2003 x64.
> if there is any issue or compatibility problem, I'll use the 32bit
> edition.
>
> <dbahooker@.hotmail.com> wrote in message
> news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
>|||Thankls.
I have all of this on my CD Roms...
so finally, there is no issue in mind(?)
"Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message
news:%23ultf2XvFHA.4032@.TK2MSFTNGP15.phx.gbl...
> If you are going to install the 64-bit version of the Win2K3 make sure:
> 1) you install SP1 of Win2K3 x64 -- and
> 2) you use SP4
> Both are required to run AS2K on x64 hardware with a 64-bit OS.
> --
> Dave Wickert [MSFT]
> dwickert@.online.microsoft.com
> Program Manager
> BI Systems Team
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Jj" <willgart_A_@.hotmail_A_.com> wrote in message
> news:ONOy27vuFHA.2072@.TK2MSFTNGP14.phx.gbl...
>|||I will be deploying this same setup... Windows 2003 Standard x64
Edition running SQL Server 2000 Enterprise Edition SP4. The server I'm
running on has 8GB of RAM. Does anyone know how much RAM SQL Server
will use? My understanding is that this is not an AWE situtation
because the OS can natively address all 8GB of RAM.
Any advice on maximizing this setup would be greatly appreciated.
Thanks.
george sarlas
gsarlas@.yahoo.com|||> My understanding is that this is not an AWE situtation
> because the OS can natively address all 8GB of RAM.
You are right, SQL Server can access up to 512Gb of RAM, which is the
maximum currently supported by Win2K3 Server.
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell|||I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
AWE in SQL Server. But to support more than 4GB of RAM, I needed to
install SQL 2000 SP4 and the SP4 AWE Hotfix
(http://support.microsoft.com/default.aspx?kbid=899761).
-georgesql

new server to install, Win 2003 x64 will be used... which SQL Version?

Hi,
I have to install a new server and I am a little confused about working
combinations between 30bits, x64 and IA64...
My server use intel Xeon processors with EMT64.
So I want to install Windows 2003 x64 Ent.
but which version of SQL Server can I install?
the 64bits?
32bits + SP4 (Sql2k64sp4.exe)?
Also I have to install Reporting Services, Analysis Services & Sharepoint.
Does everything works on Win x64?
I'm using SQL Server 2000 enterprise edition.
thanks for your answer.
Jerome.You need the SQL Server 2000 (64-bit) edition.
http://www.microsoft.com/sql/64bit/default.mspx
--
--Brian
(Please reply to the newsgroups only.)
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:e%2313sduuFHA.3764@.TK2MSFTNGP09.phx.gbl...
> Hi,
> I have to install a new server and I am a little confused about working
> combinations between 30bits, x64 and IA64...
> My server use intel Xeon processors with EMT64.
> So I want to install Windows 2003 x64 Ent.
> but which version of SQL Server can I install?
> the 64bits?
> 32bits + SP4 (Sql2k64sp4.exe)?
> Also I have to install Reporting Services, Analysis Services & Sharepoint.
> Does everything works on Win x64?
> I'm using SQL Server 2000 enterprise edition.
> thanks for your answer.
> Jerome.
>|||what you really need; you need to wait for sql 2005 and it'll be a LOT
better|||unfortunatly its an hardware migration process.
we change an old server to a new one
so we can't deploy 2005.
but I have to insure that the 64bits edition (of SQL, RS, AS) works
correctly on Win 2003 x64.
if there is any issue or compatibility problem, I'll use the 32bit edition.
<dbahooker@.hotmail.com> wrote in message
news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
> what you really need; you need to wait for sql 2005 and it'll be a LOT
> better
>|||Hi
No, 32 Bit plus SP4.
SQL Server 2000 64 Bit is complied for the Intel Itanium Processor and will
not run on Xeons.
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/
"Brian Lawton" <brian.k.lawton@.redtailcreek.com> wrote in message
news:%23QD6nsuuFHA.1472@.TK2MSFTNGP15.phx.gbl...
> You need the SQL Server 2000 (64-bit) edition.
> http://www.microsoft.com/sql/64bit/default.mspx
> --
> --Brian
> (Please reply to the newsgroups only.)
>
> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
> news:e%2313sduuFHA.3764@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> I have to install a new server and I am a little confused about working
>> combinations between 30bits, x64 and IA64...
>> My server use intel Xeon processors with EMT64.
>> So I want to install Windows 2003 x64 Ent.
>> but which version of SQL Server can I install?
>> the 64bits?
>> 32bits + SP4 (Sql2k64sp4.exe)?
>> Also I have to install Reporting Services, Analysis Services &
>> Sharepoint.
>> Does everything works on Win x64?
>> I'm using SQL Server 2000 enterprise edition.
>> thanks for your answer.
>> Jerome.
>>
>|||If you are going to install the 64-bit version of the Win2K3 make sure:
1) you install SP1 of Win2K3 x64 -- and
2) you use SP4
Both are required to run AS2K on x64 hardware with a 64-bit OS.
--
Dave Wickert [MSFT]
dwickert@.online.microsoft.com
Program Manager
BI Systems Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
news:ONOy27vuFHA.2072@.TK2MSFTNGP14.phx.gbl...
> unfortunatly its an hardware migration process.
> we change an old server to a new one
> so we can't deploy 2005.
> but I have to insure that the 64bits edition (of SQL, RS, AS) works
> correctly on Win 2003 x64.
> if there is any issue or compatibility problem, I'll use the 32bit
> edition.
>
> <dbahooker@.hotmail.com> wrote in message
> news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
>> what you really need; you need to wait for sql 2005 and it'll be a LOT
>> better
>|||Thankls.
I have all of this on my CD Roms...
so finally, there is no issue in mind(?)
"Dave Wickert [MSFT]" <dwickert@.online.microsoft.com> wrote in message
news:%23ultf2XvFHA.4032@.TK2MSFTNGP15.phx.gbl...
> If you are going to install the 64-bit version of the Win2K3 make sure:
> 1) you install SP1 of Win2K3 x64 -- and
> 2) you use SP4
> Both are required to run AS2K on x64 hardware with a 64-bit OS.
> --
> Dave Wickert [MSFT]
> dwickert@.online.microsoft.com
> Program Manager
> BI Systems Team
> SQL BI Product Unit (Analysis Services)
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Jéjé" <willgart_A_@.hotmail_A_.com> wrote in message
> news:ONOy27vuFHA.2072@.TK2MSFTNGP14.phx.gbl...
>> unfortunatly its an hardware migration process.
>> we change an old server to a new one
>> so we can't deploy 2005.
>> but I have to insure that the 64bits edition (of SQL, RS, AS) works
>> correctly on Win 2003 x64.
>> if there is any issue or compatibility problem, I'll use the 32bit
>> edition.
>>
>> <dbahooker@.hotmail.com> wrote in message
>> news:1126900439.484602.107740@.g44g2000cwa.googlegroups.com...
>> what you really need; you need to wait for sql 2005 and it'll be a LOT
>> better
>>
>|||I will be deploying this same setup... Windows 2003 Standard x64
Edition running SQL Server 2000 Enterprise Edition SP4. The server I'm
running on has 8GB of RAM. Does anyone know how much RAM SQL Server
will use? My understanding is that this is not an AWE situtation
because the OS can natively address all 8GB of RAM.
Any advice on maximizing this setup would be greatly appreciated.
Thanks.
--
george sarlas
gsarlas@.yahoo.com|||> My understanding is that this is not an AWE situtation
> because the OS can natively address all 8GB of RAM.
You are right, SQL Server can access up to 512Gb of RAM, which is the
maximum currently supported by Win2K3 Server.
--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell|||I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
AWE in SQL Server. But to support more than 4GB of RAM, I needed to
install SQL 2000 SP4 and the SP4 AWE Hotfix
(http://support.microsoft.com/default.aspx?kbid=899761).
-george|||If you have 64bit SQL 2k you do not need to enable AWE. The knowledge
base article you quote only applies to 32bit SQL 2k. 64bit SQL 2k can
address the maximum amount of memory that Win2k3 can support (which is
512Gb) without turning on any special settings.
--
Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell
In article <1130256929.245741.68610@.g44g2000cwa.googlegroups.com>,
gsarlas@.yahoo.com says...
> I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
> AWE in SQL Server. But to support more than 4GB of RAM, I needed to
> install SQL 2000 SP4 and the SP4 AWE Hotfix
> (http://support.microsoft.com/default.aspx?kbid=899761).
> -george
>|||Just for clarification...
Unfortunately, SQL Server 2000 64-bit Edition does not work with x64
processors. It only works with the Itanium processor. I am running
32-bit SQL Server 2000 on 64-bit Windows 2003, thus I had to enable
AWE.
-george
Darren Gosbell wrote:
> If you have 64bit SQL 2k you do not need to enable AWE. The knowledge
> base article you quote only applies to 32bit SQL 2k. 64bit SQL 2k can
> address the maximum amount of memory that Win2k3 can support (which is
> 512Gb) without turning on any special settings.
> --
> Regards
> Darren Gosbell [MCSD]
> <dgosbell_at_yahoo_dot_com>
> Blog: http://www.geekswithblogs.net/darrengosbell
> In article <1130256929.245741.68610@.g44g2000cwa.googlegroups.com>,
> gsarlas@.yahoo.com says...
> > I've deployed the 1st of my 2 new 64-bit servers. I did have to enable
> > AWE in SQL Server. But to support more than 4GB of RAM, I needed to
> > install SQL 2000 SP4 and the SP4 AWE Hotfix
> > (http://support.microsoft.com/default.aspx?kbid=899761).
> >
> > -george
> >
> >

New problem getting data from xml table in sql db (Newbie)

Hello,

I have this xml tablerow in a table in my db.

2 examples

<Toyconfiguration version = "1" name = "Lego">

<Ballconfiguration version = "2020" name= "Adidas">

If I would want to get the name of the toy or ball I would write

Select

Tablerow.value('((@.name)[1]', 'varchar(100)')

From table

This would return Lego and Adidas

But what if I want to know which kind of configuration it is? How do I do this?

The answer I want is Toyconfiguration and Ballconfiguration..

Any help would be appreciated!

You could use local-name() function:

select

Tablerow.xml_col.value('(//@.name)[1]', 'varchar(100)')

,Tablerow.xml_col.value('local-name((*[@.name])[1])', 'varchar(100)')

from TableRow

|||

Kontantin,

Thanks a bunch for your answer. You saved me!!!

new patch for 32 bit and 64 bit SQL server

How do you determine if a server is running the 32 bit or
64 bit version. I have seen the query to determine service
pack level but I don't see an indicator to determine if a
server is 32 bit or 64 bit. There is a different patch
dependant on this value.>--Original Message--
>Pat,
>Is it the season? lol :-)
>I just answered a similar query a while back...
>--
>Dinesh.
>SQL Server FAQ at
>http://www.tkdinesh.com
>"Pat" <mcilweep@.ctbsonline.com> wrote in message
>news:01ee01c352d6$7d4ca5c0$a301280a@.phx.gbl...
>> How do you determine if a server is running the 32 bit
or
>> 64 bit version. I have seen the query to determine
service
>> pack level but I don't see an indicator to determine if
a
>> server is 32 bit or 64 bit. There is a different patch
>> dependant on this value.
>
>.
>I appreciate your reply but still don't see the info I
need. I found the info about determining the SP of SQL on
your website FAQ's, but I don't see anything that
indicates that it is a 32 bit or 64 bit system. What am I
missing?|||Pat,
May be I got carried away because I answered couple of similar posts
one-by-one in .server :-) The latest one was by Aparna Rege.Anyways, this is
the info:
You should be able to tell by running a SELECT @.@.version against your SQL
Server.
On 32-bit, you will see the following:
Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.1 (Build 2600: Service Pack 1)
On 64-bit, the architecture should be Intel IA-64
Microsoft SQL Server 2000 - 8.00.818 (Intel IA-64)
Thanks to : Arvind Krishnan
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Pat" <mcilweep@.ctbsonline.com> wrote in message
news:03cb01c352e6$10f67990$a101280a@.phx.gbl...
> >--Original Message--
> >Pat,
> >
> >Is it the season? lol :-)
> >
> >I just answered a similar query a while back...
> >
> >--
> >Dinesh.
> >SQL Server FAQ at
> >http://www.tkdinesh.com
> >
> >"Pat" <mcilweep@.ctbsonline.com> wrote in message
> >news:01ee01c352d6$7d4ca5c0$a301280a@.phx.gbl...
> >> How do you determine if a server is running the 32 bit
> or
> >> 64 bit version. I have seen the query to determine
> service
> >> pack level but I don't see an indicator to determine if
> a
> >> server is 32 bit or 64 bit. There is a different patch
> >> dependant on this value.
> >
> >
> >.
> >I appreciate your reply but still don't see the info I
> need. I found the info about determining the SP of SQL on
> your website FAQ's, but I don't see anything that
> indicates that it is a 32 bit or 64 bit system. What am I
> missing?

New Installation of SQL Server 2000

Hi,
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBA
Newbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com

New Installation of SQL Server 2000

Hi,
I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not support on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New SQL Server DBANewbie wrote:
> Hi,
> I installed sql server 2000 sp2 standard edition on Windows 2003, when
> installing, it said "This version is not support on this os", but I
> was told to continue installing the software and that I could install
> the latest security patches to bring it up to date. Will that work?
> Do I need to do anything else? SQL Server 2000 is up and running on
> the box. When running the statement " select @.@.version" it informed
> me that I was at 8.00.194 patch level. How can I tell if SQL Server
> 2000 is 32 or 64 bit? I was trying to download the lasted patch and
> it asked for that info. Thanks.-- New SQL Server DBA
You didn't install SQL 2000 SP2. You installed SQL 2000 RTM (v194). The
installation program at the point SQL 2000 RTM was released didn't know
about Win2K3 and is giving you the error.
Install SP3a on the server and you should be ready to go.
David Gugick
Imceda Software
www.imceda.com

New Installation of Sql Server 2000

Hello Guru's, I need your help!

I installed sql server 2000 sp2 standard edition on Windows 2003, when
installing, it said "This version is not supported on this os", but I was told
to continue installing the software and that I could install the latest
security patches to bring it up to date. Will that work? Do I need to do
anything else? SQL Server 2000 is up and running on the box. When running
the statement " select @.@.version" it informed me that I was at 8.00.194
patch level. How can I tell if SQL Server 2000 is 32 or 64 bit? I was
trying to download the lasted patch and it asked for that info. Thanks.--
New to SQL ServerUnless you paid over $20,000 for SQL Server, it is probably 32 bit. I think the 64 bit version of SQL server states in @.@.version that it is 64 bit, so if you do not see anything, you very likely have 32 bit.

You need SQL Server SP3 to run on Windows 2003 with no problems. Just download the patch, run it, and you should be all set.|||Thank You Very Much!!! :)