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 SQL Datatypes

I started experimenting with SQL Server 2008, June CTP. So the first thing I tried to do is to create a new table having as column types the new datatypes available in Katmai. According to a MS white paper new sql data types include Filestream, Date, Time. Does June CTP include those new types? Am I making a wrong assumption?

Thank you

All the new datatypes are scheduled for a later release, so unfortunately we'll just have to wait.

The what's new section i BOL is pretty handy if you wonder what you can play with

|||As referred you might have to wait or see for next 2 CTP releases on the changes, if you have observed in Katmai BOL or not there are blank placeholders for such features inclusion or make them deprecated based upon the CONNECT feedback or by popularity.sql

New Server Registration to External Database

Hi All,

Quick question ...

Is it possible to add an external server registration using SQL Server Management Studio Express CTP?

Reason being I have been doing some work from home and need to port the data back to the office who are on SQL 2000. I have a database with my web hosting company and wanted to export the data to the 'live' database so I could import to the office database - any ideas?

I've tried to connect using my login details and I know the live DB is operational as I can connect through my work system. I just can't seem to be able to do it on my system at home.

Any help would be greatly appreciated as it's been a real pain to get stuff transferred. I've so far had to generate SQL script to create the procs and tables for when I get to work - the proper down side is that I lose the content of the tables which not much right now but will be loads soon!

Many Thanks

--

I have just dicovered that the CTP management studio will not connect to SQL 7 - is there any alternative or does the new version compensate for this?

There is now way to connect to SQL Server 7 in Management Studio(Express Edition or otherwise).

If you want to move the data from 2005 to 2000/7 your best bet is BCP or DTS/SSIS

|||

I'm afraid you will have to excuse my ignorance here as I am not a terribly experienced user of SQL Server. I've only be developing for the last year and a half and have always been able to use Enterprise Manager at work as everything is SQL 2000. This fortunately also connects to SQL 7 but SQL 2005 Express rather conveniently appears to have no easy backward compatibility.

So - what is BCP, DTS/SSIS and where might I find them on SQL 2005 Management Studio CTP - if that's where I should be looking?

So far, in order to migrate the structure of a database from 2005 to 2000 I have had to generate SQL scripts to create the tables and procs. A bit of a nightmare as I lose all data this way. Will the above solution resolve this issue?

Many Thanks

|||

First step is to upgrade from the CTP to the production version...

If you have the scripts then you now need the data, there are 2 choices, use whats called a linked server(Books On Line can help you try this out) or you can generate text files using BCP. DTS/SSIS is not available if you are pushing the data from a 2005 server, however you could try pulling it from the 2005 to the 7 server on the 7 server, ie have DTS in 7.0 connect to 2005.

BTW in your statement above you are mixing up the tools and the products...

EM and QA come with SQL 7 and 2000, the 2000 versions work with 7 and 2000.

SSMS comes with SQL 2005, it works with 2005 and 2000.

Once you have a database in a higher version (2000 or 2005) there is no easy way to go back to an older version (7 or 2000)

New Server Registration to External Database

Hi All,

Quick question ...

Is it possible to add an external server registration using SQL Server Management Studio Express CTP?

Reason being I have been doing some work from home and need to port the data back to the office who are on SQL 2000. I have a database with my web hosting company and wanted to export the data to the 'live' database so I could import to the office database - any ideas?

I've tried to connect using my login details and I know the live DB is operational as I can connect through my work system. I just can't seem to be able to do it on my system at home.

Any help would be greatly appreciated as it's been a real pain to get stuff transferred. I've so far had to generate SQL script to create the procs and tables for when I get to work - the proper down side is that I lose the content of the tables which not much right now but will be loads soon!

Many Thanks

--

I have just dicovered that the CTP management studio will not connect to SQL 7 - is there any alternative or does the new version compensate for this?

There is now way to connect to SQL Server 7 in Management Studio(Express Edition or otherwise).

If you want to move the data from 2005 to 2000/7 your best bet is BCP or DTS/SSIS

|||

I'm afraid you will have to excuse my ignorance here as I am not a terribly experienced user of SQL Server. I've only be developing for the last year and a half and have always been able to use Enterprise Manager at work as everything is SQL 2000. This fortunately also connects to SQL 7 but SQL 2005 Express rather conveniently appears to have no easy backward compatibility.

So - what is BCP, DTS/SSIS and where might I find them on SQL 2005 Management Studio CTP - if that's where I should be looking?

So far, in order to migrate the structure of a database from 2005 to 2000 I have had to generate SQL scripts to create the tables and procs. A bit of a nightmare as I lose all data this way. Will the above solution resolve this issue?

Many Thanks

|||

First step is to upgrade from the CTP to the production version...

If you have the scripts then you now need the data, there are 2 choices, use whats called a linked server(Books On Line can help you try this out) or you can generate text files using BCP. DTS/SSIS is not available if you are pushing the data from a 2005 server, however you could try pulling it from the 2005 to the 7 server on the 7 server, ie have DTS in 7.0 connect to 2005.

BTW in your statement above you are mixing up the tools and the products...

EM and QA come with SQL 7 and 2000, the 2000 versions work with 7 and 2000.

SSMS comes with SQL 2005, it works with 2005 and 2000.

Once you have a database in a higher version (2000 or 2005) there is no easy way to go back to an older version (7 or 2000)

New features/bug fixes in Sept CTP?

Does anyone know where I can find a list of new features/bug fixes in the Sept CTP? I've been having a hard time tracking down this info. If someone could post it that would be great!
Thanks,
Adrian
Anyone know if this list exists? I'd be keen to see it.

-Jamie|||Can we request someone from SSIS team to post such a list. It will be helpful for all.

thanks,
Nitesh|||It would be very hard to combine a list of all the changes
SSIS team did in 3 months (plus all the changes .NET &
Visual Studio teams did in 5 months).

Mostly the changes are bug fixes, stability and performance
improvements. Very little new features, no new tasks or
transforms for sure .|||

Michael Entin SSIS wrote:

It would be very hard to combine a list of all the changes
SSIS team did in 3 months (plus all the changes .NET &
Visual Studio teams did in 5 months).

Mostly the changes are bug fixes, stability and performance
improvements. Very little new features, no new tasks or
transforms for sure .

Sorry to labour the point Michael

Bug fixing isn't very interesting but I'm interested in performance. What has changed there? Is it pipeline engine perf, runtime engine perf or design tools perf?

-Jamie|||Well, lots of the bugs at this stage are about performance.

I can say about my area - we fixed memory leaks in designer
and project code, so now it should be possible to keep
designer tools open for long time (the memory usage used
to grow over time before).

I know about performance problems fixes in some data flow
component UIs also.|||Bugs found in Sept CTP

I found that I couldn't drag items from the toolbox to the control flow. Had to double click on the items.

The Variables view has a problem displaying itself when associated with an autohide pane.

Loads of exceptions when debugging a custom component, (really annoying)

Devenv crashes when trying to debug a devenv instance with SSIS already loaded into it.

Not much really

oh found a few previously found bugs have been fixed :)|||I'm trying to get the ability to get a list of externally reported bugs that have been fixed in a particular CTP. For what it's worth, I'm told this is on the list of items to provide in the future.

regards,
ash

New CTP

Will there be an August CTP of Sql Server 2005?

What interim version do you still plan on releasing before RTM on November 7th?

Hi,

in the internet I read something about a beta 3.

|||Beta 3 was another name for the June CTP (which doesn't work on DCs!), Microsoft announced that they would only create CTP's before the final release... So I really hope we can expect one soon, if only to test if everything works correctly now on domain controllers...

Can someone from Microsoft please give us an update?|||

I can say that we're discussing releasing another CTP prior to RTM but I can't say for certain if this will happen and if it does when. Sorry for being so vague.

Dan