I'm trying to understand Datawarehousing in the MS SQL World.
I'm a SAS Developer and have read reams of information on MSDN about Microso
fts Approach and DTS. But if I want to run a completely automated system in
Batch, is DTS still the approach.
Can anyone suggest a really good course in the UK or Book that might help?
I can see that SQL is a great tool as I've been getting used to it by contro
lling it from SAS - now I just want to go that little bit further.
Do I need to develop my own environment in VB.NET ?
Please help I'm getting overloaded with MS's TLAs and now need someone to te
ll me exactly what is neededHey, have u looked at www.swldts.com
--
SQL Server MVP - Colombia
"Jason Duncan-King" wrote:
> I'm trying to understand Datawarehousing in the MS SQL World.
> I'm a SAS Developer and have read reams of information on MSDN about Micro
softs Approach and DTS. But if I want to run a completely automated system
in Batch, is DTS still the approach.
> Can anyone suggest a really good course in the UK or Book that might help?
> I can see that SQL is a great tool as I've been getting used to it by cont
rolling it from SAS - now I just want to go that little bit further.
> Do I need to develop my own environment in VB.NET ?
> Please help I'm getting overloaded with MS's TLAs and now need someone to tell me
exactly what is needed|||In article <679321A7-CC23-43C8-A6A0-3CC74A543653@.microsoft.com>,
Alejandro Leguizamo (MVP) wrote:
> Hey, have u looked at www.swldts.com
>
www.sqldts.com right?
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
www.konesans.com - for all your consultancy needssql
Showing posts with label msdn. Show all posts
Showing posts with label msdn. Show all posts
Friday, March 30, 2012
New to SQL - Old SAS School
I'm trying to understand Datawarehousing in the MS SQL World.
I'm a SAS Developer and have read reams of information on MSDN about Microsofts Approach and DTS. But if I want to run a completely automated system in Batch, is DTS still the approach.
Can anyone suggest a really good course in the UK or Book that might help?
I can see that SQL is a great tool as I've been getting used to it by controlling it from SAS - now I just want to go that little bit further.
Do I need to develop my own environment in VB.NET ?
Please help I'm getting overloaded with MS's TLAs and now need someone to tell me exactly what is needed
Hey, have u looked at www.swldts.com
SQL Server MVP - Colombia
"Jason Duncan-King" wrote:
> I'm trying to understand Datawarehousing in the MS SQL World.
> I'm a SAS Developer and have read reams of information on MSDN about Microsofts Approach and DTS. But if I want to run a completely automated system in Batch, is DTS still the approach.
> Can anyone suggest a really good course in the UK or Book that might help?
> I can see that SQL is a great tool as I've been getting used to it by controlling it from SAS - now I just want to go that little bit further.
> Do I need to develop my own environment in VB.NET ?
> Please help I'm getting overloaded with MS's TLAs and now need someone to tell me exactly what is needed
|||In article <679321A7-CC23-43C8-A6A0-3CC74A543653@.microsoft.com>,
Alejandro Leguizamo (MVP) wrote:
> Hey, have u looked at www.swldts.com
>
www.sqldts.com right?
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
www.konesans.com - for all your consultancy needs
I'm a SAS Developer and have read reams of information on MSDN about Microsofts Approach and DTS. But if I want to run a completely automated system in Batch, is DTS still the approach.
Can anyone suggest a really good course in the UK or Book that might help?
I can see that SQL is a great tool as I've been getting used to it by controlling it from SAS - now I just want to go that little bit further.
Do I need to develop my own environment in VB.NET ?
Please help I'm getting overloaded with MS's TLAs and now need someone to tell me exactly what is needed
Hey, have u looked at www.swldts.com
SQL Server MVP - Colombia
"Jason Duncan-King" wrote:
> I'm trying to understand Datawarehousing in the MS SQL World.
> I'm a SAS Developer and have read reams of information on MSDN about Microsofts Approach and DTS. But if I want to run a completely automated system in Batch, is DTS still the approach.
> Can anyone suggest a really good course in the UK or Book that might help?
> I can see that SQL is a great tool as I've been getting used to it by controlling it from SAS - now I just want to go that little bit further.
> Do I need to develop my own environment in VB.NET ?
> Please help I'm getting overloaded with MS's TLAs and now need someone to tell me exactly what is needed
|||In article <679321A7-CC23-43C8-A6A0-3CC74A543653@.microsoft.com>,
Alejandro Leguizamo (MVP) wrote:
> Hey, have u looked at www.swldts.com
>
www.sqldts.com right?
Allan Mitchell (Microsoft SQL Server MVP)
MCSE,MCDBA
www.SQLDTS.com
www.konesans.com - for all your consultancy needs
Monday, March 26, 2012
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.
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.
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
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 SQLXMLBulkLoad user--having problems
I am trying, for the first time to load an xml file into SQL Server 2000, and to get me going I am trying to execute the msdn example:-
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlxml3/htm/bulkload_6bos.asp
I have configured all the needed set up and keep getting this error:-
Automation error(80040e21)
With no real error info in the error log
The Connection string details are all correct..I have checked that
The error occurs at line:-
objBL.Execute "SampleSchema.xml", "SampleXMLData.xml"
Have you got any ideas…?
Has anyone actually managed to run this example without errors?
Appreciate your help
Thanks
Raj
Hello,
Send me the schema and the data file and I will try a repro.
Regards,
Monica
sqlNew SQLXMLBulkLoad user--having problems
I am trying, for the first time to load an xml file into SQL Server 2000, and to get me going I am trying to execute the msdn example:-
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sqlxml3/htm/bulkload_6bos.asp
I have configured all the needed set up and keep getting this error:-
Automation error(80040e21)
With no real error info in the error log
The Connection string details are all correct..I have checked that
The error occurs at line:-
objBL.Execute "SampleSchema.xml", "SampleXMLData.xml"
Have you got any ideas…?
Has anyone actually managed to run this example without errors?
Appreciate your help
Thanks
Raj
Hello,
Send me the schema and the data file and I will try a repro.
Regards,
Monica
Friday, March 23, 2012
NEW SQL Server Release`
Check this out
this is the replacement for MSDE 2000
SQL Server 2005 Express Edition (http://lab.msdn.microsoft.com/express/sql/default.aspx)
Top 10 cool things about SQL Server Express Edition (http://lab.msdn.microsoft.com/express/sql/top10/default.aspx)
SQL Server Express Books Online (http://www.microsoft.com/downloads/details.aspx?FamilyId=2ADBC1A8-AE5C-497D-B584-EAB6719300CD&displaylang=en)
by the way if you follow the first link, you will find a pretty accurate photo of rdjabarov...Check this out
you will find a pretty accurate photo of rdjabarov...
Looks pretty nice and decent just like the Express Edition. Where he's from by the way, USA!!|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?|||Hey now, I'm from Ala-freaking-bama|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?
i'm just kidding
but on further reflection he kind of looks like fabian pascal.
Pat can verify that for us because as we all know, he's fabian's best friend.|||Do you really believe that I think that way?..Well, I DO love Texas, but I am ready for a change (ideally would be to move without my kids knowing where to :D )|||Anyone else think that CLR is a bunch of nonsense?|||Anyone else think that CLR is a bunch of nonsense?
I think it's VERY neat. I also think that this will force some hard core production DBA's to have a hard look at themselves and see if the career they've chosen is what they want to continue pursuing. Personally, I am happy with a definition that is given to me, - hybrid DBA! And the direction the job description is taking is where I am at now.|||Pat can verify that for us because as we all know, he's fabian's best friend.It's good to be loved, isn't it? Actually, I've never met Fabian in person, or even seen a picture from a reliable source, so I'm no authority there. It's hard to imagine that I've never seen anyone that loves me so, isn't it?
-PatP|||Anyone else think that CLR is a bunch of nonsense?Not really, I think that the CLR brings a lot of interesting benefits, but it brings some new risks in the baggage with it.
The benefits are basically the ones that UCSD promised with the p-machine and Java didn't quite deliver with their virtual machine. A standard, more or less hardware independant virtual machine. One code base for many platforms. One target for many compilers, which allows much better tools to evolve because the economies of scale kick in much sooner.
The big risks seem to be that once something makes it into the runtime, who will ensure that it makes sense for it to stay there as it evolves. Many things that make perfect sense on the desktop (or even handheld) are a positive liability on a server!
It is a two edged sword. It brings many benefits, but at a significant cost.
-PatP|||I think it's VERY neat.
Why? And yes, PROD DBA's who sit there waiting for an alert...sure...but someones got to do that...and I'm glad it's not me...not sure if they even know what a sproc is...let alone a trigger...
And what can you do with "External Procedures" (CLR) that you can't do with T-SQL or it's extensions?
CLR is just more overhead...
And I'd love to see what they mean by Extensive XML support...
What? Did they add Relational extenders to XML?|||Well, I've run to the rescue of "External Procedures" via sp_oaxxx. You're write, the same thing can be accomplished by T-SQL, but the final choice is based on many factors. I prefer to use a tool for a task that is designed to do that task. Of course I can create a file using T-SQL, but if there is a better way to do the same thing (Scripting.FileSystemObject) I'd pick that one.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)|||I think Pat summed it up pretty well. There are some things that the CLR will just do better. There's also a LOT of risk if it's used wrong. The XML thing actually worries me more then the CLR though. It's harking back to the days of hierarchial design and promising "extensibility". I have a feeling we'll end up regretting the degradation of a relational environment to cater to the desires of a shortcut "extend into anything without considering the consequences" world. Oh well....rant off.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)
Right on, man, right on!
this is the replacement for MSDE 2000
SQL Server 2005 Express Edition (http://lab.msdn.microsoft.com/express/sql/default.aspx)
Top 10 cool things about SQL Server Express Edition (http://lab.msdn.microsoft.com/express/sql/top10/default.aspx)
SQL Server Express Books Online (http://www.microsoft.com/downloads/details.aspx?FamilyId=2ADBC1A8-AE5C-497D-B584-EAB6719300CD&displaylang=en)
by the way if you follow the first link, you will find a pretty accurate photo of rdjabarov...Check this out
you will find a pretty accurate photo of rdjabarov...
Looks pretty nice and decent just like the Express Edition. Where he's from by the way, USA!!|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?|||Hey now, I'm from Ala-freaking-bama|||Hey, you see what you started, Scott? And YOU KNOW I don't look like this!.. And where the h*** did you get 2005 Express? In Ala-freaking-bama?
i'm just kidding
but on further reflection he kind of looks like fabian pascal.
Pat can verify that for us because as we all know, he's fabian's best friend.|||Do you really believe that I think that way?..Well, I DO love Texas, but I am ready for a change (ideally would be to move without my kids knowing where to :D )|||Anyone else think that CLR is a bunch of nonsense?|||Anyone else think that CLR is a bunch of nonsense?
I think it's VERY neat. I also think that this will force some hard core production DBA's to have a hard look at themselves and see if the career they've chosen is what they want to continue pursuing. Personally, I am happy with a definition that is given to me, - hybrid DBA! And the direction the job description is taking is where I am at now.|||Pat can verify that for us because as we all know, he's fabian's best friend.It's good to be loved, isn't it? Actually, I've never met Fabian in person, or even seen a picture from a reliable source, so I'm no authority there. It's hard to imagine that I've never seen anyone that loves me so, isn't it?
-PatP|||Anyone else think that CLR is a bunch of nonsense?Not really, I think that the CLR brings a lot of interesting benefits, but it brings some new risks in the baggage with it.
The benefits are basically the ones that UCSD promised with the p-machine and Java didn't quite deliver with their virtual machine. A standard, more or less hardware independant virtual machine. One code base for many platforms. One target for many compilers, which allows much better tools to evolve because the economies of scale kick in much sooner.
The big risks seem to be that once something makes it into the runtime, who will ensure that it makes sense for it to stay there as it evolves. Many things that make perfect sense on the desktop (or even handheld) are a positive liability on a server!
It is a two edged sword. It brings many benefits, but at a significant cost.
-PatP|||I think it's VERY neat.
Why? And yes, PROD DBA's who sit there waiting for an alert...sure...but someones got to do that...and I'm glad it's not me...not sure if they even know what a sproc is...let alone a trigger...
And what can you do with "External Procedures" (CLR) that you can't do with T-SQL or it's extensions?
CLR is just more overhead...
And I'd love to see what they mean by Extensive XML support...
What? Did they add Relational extenders to XML?|||Well, I've run to the rescue of "External Procedures" via sp_oaxxx. You're write, the same thing can be accomplished by T-SQL, but the final choice is based on many factors. I prefer to use a tool for a task that is designed to do that task. Of course I can create a file using T-SQL, but if there is a better way to do the same thing (Scripting.FileSystemObject) I'd pick that one.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)|||I think Pat summed it up pretty well. There are some things that the CLR will just do better. There's also a LOT of risk if it's used wrong. The XML thing actually worries me more then the CLR though. It's harking back to the days of hierarchial design and promising "extensibility". I have a feeling we'll end up regretting the degradation of a relational environment to cater to the desires of a shortcut "extend into anything without considering the consequences" world. Oh well....rant off.|||i like the concept and intent of the Common Language Runtime.
now you can develop in your native language without having to learn an entirely new discipline.
standardization is a good thing. it allows developers to get back to the act of developing logic instead of all of these funky diversions that we have to endure.
case in point --dbforums.com
what percent of all of the questions raised here are by dba's to dba's about dba stuff.
most of them are actually developers trying to reinvent the wheel in a entirely new discipline (T-sql SQL Server etc..). by giving them a internal wrapper for all of their "stuff" they can truly screw everything up and then call us "The Consultant" to fix it (for a fee of course)
Right on, man, right on!
New SQL Server Registration
Hello,
I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
new SQL Server Registration. Any help with this would be appreciated.
--
Thanks in advance,
sck10What exactly is the problem?
Try View, Registered Servers. Click and then right-click Database Engine,
New, Server Registration. Complete the data, Test and Save.
Ben Nevarez, MCDBA, OCP
Database Administrator
"sck10" wrote:
> Hello,
> I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
> new SQL Server Registration. Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>
>
I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
new SQL Server Registration. Any help with this would be appreciated.
--
Thanks in advance,
sck10What exactly is the problem?
Try View, Registered Servers. Click and then right-click Database Engine,
New, Server Registration. Complete the data, Test and Save.
Ben Nevarez, MCDBA, OCP
Database Administrator
"sck10" wrote:
> Hello,
> I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
> new SQL Server Registration. Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>
>
New SQL Server Registration
Hello,
I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
new SQL Server Registration. Any help with this would be appreciated.
--
Thanks in advance,
sck10What exactly is the problem?
Try View, Registered Servers. Click and then right-click Database Engine,
New, Server Registration. Complete the data, Test and Save.
Ben Nevarez, MCDBA, OCP
Database Administrator
"sck10" wrote:
> Hello,
> I just installed SS2K5 Developer's edition (MSDN). I am unable to create
a
> new SQL Server Registration. Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>
>
I just installed SS2K5 Developer's edition (MSDN). I am unable to create a
new SQL Server Registration. Any help with this would be appreciated.
--
Thanks in advance,
sck10What exactly is the problem?
Try View, Registered Servers. Click and then right-click Database Engine,
New, Server Registration. Complete the data, Test and Save.
Ben Nevarez, MCDBA, OCP
Database Administrator
"sck10" wrote:
> Hello,
> I just installed SS2K5 Developer's edition (MSDN). I am unable to create
a
> new SQL Server Registration. Any help with this would be appreciated.
> --
> Thanks in advance,
> sck10
>
>
Subscribe to:
Posts (Atom)