AS2005 September CTP Memory Error

I get "Memory error: While attempting to store a string, a string was found that was larger than the page size selected. The operation cannot be completed." while executing query set with cube browser in SQL Server BI Dev Studio. The same error I get while executing query with VB code (via ADOMD). The source of the error is AS2005 OLEDB Provider.

One important information: I have installed Sept CTP on clean Windows XP Pro, there were no previous versions of SQL 2005 installed.

Any ideas what's up? Maybe some missing parameter in connection string?I'm having the same problem after I uninstalled the June CTP and installed Sept CTP. I'm getting the error in BIDS and SSMS, I can browse dimensions but when I try to drag a dimension or measure onto cube browser I get the error. I tried deleting the AS database, redeploying, and reprocessing and I'm still getting the error. Any help would be appreciated.|||

From another message board:

This is a known issue with the September CTP and it has been fixed in
post-CTP builds. The problem surfaces with client-side record sizes greater
than 1k, so a possible workaround might be to rework the cube structure to
reduce record sizes.

--
-Raman Iyer
[This posting is provided "AS IS" with no warranties, and confers no
rights.]

|||Trying to work thru the as2005 tutorial and am stopped by said memory issue.

Any solutions to this? Any measure,dimension that i use causes the problem.
Reworking the cube structure to reduce record sizes? Anyone been successfull w/ that?

Are there any post-CTP (september) builds available
thanks

|||ttt

Same problem here.

There seems, however, to be some users on the forum who have gotten through the AS2005 tutorial without a hitch. I would assume these people did not have to reduce record sizes or anything like that.

Has anyone had any luck yet? Has anyone tried building a cube from non-AdventureWorks data? I tried but had a problem deploying so I didn't get to even test the memory error.

Anyone from MS have a solution or workaround?|||I encountered this very same error. Can you tell me where I could find a post-CTP build?|||Same problem here. Was this functionality available in earlier betas, and did it work properly? I suppose that would be far easier than trying to get a NEWER build...
|||I have built and depolyed a non-Adventureworks cube on September CTP with no problems at all.

|||I tried deploying a cube from a SQL 2000 data source using the September CTP, but ran into the same problem. Do you have any idea whether your successful deployment had a smaller string size and if so how it got one?
|||I currently use April CTP and everything works fine. I encountered two minor problems: slow first initialization of metadata during reading it with ADOMD (not NET) and there is no way to get value of unary operator property of member.

Best regards!|||Yup. Same here. Any chance of a hotfix or something? This basically halts SSAS development for my team on Sept CTP (we will have to roll back :P)
|||

Luther Smith wrote:

I tried deploying a cube from a SQL 2000 data source using the September CTP, but ran into the same problem. Do you have any idea whether your successful deployment had a smaller string size and if so how it got one?

Sorry, I wasn't specific enough - I just meant that I had deployed non-AdventureWorks cubes sucessfully on SeptCTP. I don't know how to find out the string size, but if you tell me, I'll check it out and let y'all know.

disclaimer - I'm using SQL2005 Sept CTP x64|||

Same problem here.

I've been trying to track this down for a few days now. The problem is reportably fixed in the Nov release, but no hot fix is available.

Based on some configuration testing, the problem appears to be in either the PTS layer or specifically in the OLE DB drivers. I managed to recreate the issue in the June CTP (CTP 15) configuration, where the Sept drivers were installed. I could access the server fine from a remote PC, but localling, the error poped up.

|||

Is there a download for the hotfix? It seems ridiculous to have to back out the CTP16 or to have to wait until the RTM is released. I need to start developing on SSAS 2005 immediately. Help?

|||I agree. I have gone through all sorts of uninstalls and reinstalls between the June and September CTP's. Nothing worked to get past the memory error. I need to start learning 2005 right away!

AS2005 September CTP Memory Error

I get "Memory error: While attempting to store a string, a string was found that was larger than the page size selected. The operation cannot be completed." while executing query set with cube browser in SQL Server BI Dev Studio. The same error I get while executing query with VB code (via ADOMD). The source of the error is AS2005 OLEDB Provider.

One important information: I have installed Sept CTP on clean Windows XP Pro, there were no previous versions of SQL 2005 installed.

Any ideas what's up? Maybe some missing parameter in connection string?I'm having the same problem after I uninstalled the June CTP and installed Sept CTP. I'm getting the error in BIDS and SSMS, I can browse dimensions but when I try to drag a dimension or measure onto cube browser I get the error. I tried deleting the AS database, redeploying, and reprocessing and I'm still getting the error. Any help would be appreciated.|||

From another message board:

This is a known issue with the September CTP and it has been fixed in
post-CTP builds. The problem surfaces with client-side record sizes greater
than 1k, so a possible workaround might be to rework the cube structure to
reduce record sizes.

--
-Raman Iyer
[This posting is provided "AS IS" with no warranties, and confers no
rights.]

|||Trying to work thru the as2005 tutorial and am stopped by said memory issue.

Any solutions to this? Any measure,dimension that i use causes the problem.
Reworking the cube structure to reduce record sizes? Anyone been successfull w/ that?

Are there any post-CTP (september) builds available
thanks|||ttt

Same problem here.

There seems, however, to be some users on the forum who have gotten through the AS2005 tutorial without a hitch. I would assume these people did not have to reduce record sizes or anything like that.

Has anyone had any luck yet? Has anyone tried building a cube from non-AdventureWorks data? I tried but had a problem deploying so I didn't get to even test the memory error.

Anyone from MS have a solution or workaround?|||I encountered this very same error. Can you tell me where I could find a post-CTP build?|||Same problem here. Was this functionality available in earlier betas, and did it work properly? I suppose that would be far easier than trying to get a NEWER build...|||I have built and depolyed a non-Adventureworks cube on September CTP with no problems at all.|||I tried deploying a cube from a SQL 2000 data source using the September CTP, but ran into the same problem. Do you have any idea whether your successful deployment had a smaller string size and if so how it got one?|||I currently use April CTP and everything works fine. I encountered two minor problems: slow first initialization of metadata during reading it with ADOMD (not NET) and there is no way to get value of unary operator property of member.

Best regards!|||Yup. Same here. Any chance of a hotfix or something? This basically halts SSAS development for my team on Sept CTP (we will have to roll back :P)|||

Luther Smith wrote:

I tried deploying a cube from a SQL 2000 data source using the September CTP, but ran into the same problem. Do you have any idea whether your successful deployment had a smaller string size and if so how it got one?

Sorry, I wasn't specific enough - I just meant that I had deployed non-AdventureWorks cubes sucessfully on SeptCTP. I don't know how to find out the string size, but if you tell me, I'll check it out and let y'all know.

disclaimer - I'm using SQL2005 Sept CTP x64|||

Same problem here.

I've been trying to track this down for a few days now. The problem is reportably fixed in the Nov release, but no hot fix is available.

Based on some configuration testing, the problem appears to be in either the PTS layer or specifically in the OLE DB drivers. I managed to recreate the issue in the June CTP (CTP 15) configuration, where the Sept drivers were installed. I could access the server fine from a remote PC, but localling, the error poped up.

|||

Is there a download for the hotfix? It seems ridiculous to have to back out the CTP16 or to have to wait until the RTM is released. I need to start developing on SSAS 2005 immediately. Help?

|||I agree. I have gone through all sorts of uninstalls and reinstalls between the June and September CTP's. Nothing worked to get past the memory error. I need to start learning 2005 right away!

AS2005 September CTP Memory Error

I get "Memory error: While attempting to store a string, a string was found that was larger than the page size selected. The operation cannot be completed." while executing query set with cube browser in SQL Server BI Dev Studio. The same error I get while executing query with VB code (via ADOMD). The source of the error is AS2005 OLEDB Provider.

One important information: I have installed Sept CTP on clean Windows XP Pro, there were no previous versions of SQL 2005 installed.

Any ideas what's up? Maybe some missing parameter in connection string?I'm having the same problem after I uninstalled the June CTP and installed Sept CTP. I'm getting the error in BIDS and SSMS, I can browse dimensions but when I try to drag a dimension or measure onto cube browser I get the error. I tried deleting the AS database, redeploying, and reprocessing and I'm still getting the error. Any help would be appreciated.|||

From another message board:

This is a known issue with the September CTP and it has been fixed in
post-CTP builds. The problem surfaces with client-side record sizes greater
than 1k, so a possible workaround might be to rework the cube structure to
reduce record sizes.

--
-Raman Iyer
[This posting is provided "AS IS" with no warranties, and confers no
rights.]

|||Trying to work thru the as2005 tutorial and am stopped by said memory issue.

Any solutions to this? Any measure,dimension that i use causes the problem.
Reworking the cube structure to reduce record sizes? Anyone been successfull w/ that?

Are there any post-CTP (september) builds available
thanks

|||ttt

Same problem here.

There seems, however, to be some users on the forum who have gotten through the AS2005 tutorial without a hitch. I would assume these people did not have to reduce record sizes or anything like that.

Has anyone had any luck yet? Has anyone tried building a cube from non-AdventureWorks data? I tried but had a problem deploying so I didn't get to even test the memory error.

Anyone from MS have a solution or workaround?|||I encountered this very same error. Can you tell me where I could find a post-CTP build?|||Same problem here. Was this functionality available in earlier betas, and did it work properly? I suppose that would be far easier than trying to get a NEWER build...
|||I have built and depolyed a non-Adventureworks cube on September CTP with no problems at all.

|||I tried deploying a cube from a SQL 2000 data source using the September CTP, but ran into the same problem. Do you have any idea whether your successful deployment had a smaller string size and if so how it got one?
|||I currently use April CTP and everything works fine. I encountered two minor problems: slow first initialization of metadata during reading it with ADOMD (not NET) and there is no way to get value of unary operator property of member.

Best regards!|||Yup. Same here. Any chance of a hotfix or something? This basically halts SSAS development for my team on Sept CTP (we will have to roll back :P)
|||

Luther Smith wrote:

I tried deploying a cube from a SQL 2000 data source using the September CTP, but ran into the same problem. Do you have any idea whether your successful deployment had a smaller string size and if so how it got one?

Sorry, I wasn't specific enough - I just meant that I had deployed non-AdventureWorks cubes sucessfully on SeptCTP. I don't know how to find out the string size, but if you tell me, I'll check it out and let y'all know.

disclaimer - I'm using SQL2005 Sept CTP x64|||

Same problem here.

I've been trying to track this down for a few days now. The problem is reportably fixed in the Nov release, but no hot fix is available.

Based on some configuration testing, the problem appears to be in either the PTS layer or specifically in the OLE DB drivers. I managed to recreate the issue in the June CTP (CTP 15) configuration, where the Sept drivers were installed. I could access the server fine from a remote PC, but localling, the error poped up.

|||

Is there a download for the hotfix? It seems ridiculous to have to back out the CTP16 or to have to wait until the RTM is released. I need to start developing on SSAS 2005 immediately. Help?

|||I agree. I have gone through all sorts of uninstalls and reinstalls between the June and September CTP's. Nothing worked to get past the memory error. I need to start learning 2005 right away!

AS2005 September CTP Errors when Processing Cube

I have a cube which was originally created in the June 2005 CTP.

I have made no changes. I am just attempting to process it in the AS2005 September CTP.

I get random messages like this:

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_PolicyFact, Column: PolicyDimKey, Value: 3135. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Policy Number of Dimension: PolicyA from Database: CDEV15D1, Cube: Cube, Measure Group: Policy Fact, Partition: Policy Fact, Record: 2920.

While trying to process various fact tables. Any ideas? I checked and the key relationships in the source store are all good.

Thanks,

ChrisI had the same problem. The cube processed fine on June CTP but would not process on the September CTP. I discovered my problem was due to the way dimension key errors were handled.

For the "key not found" option on the dimension key errors tab of the processing box, change the default setting from "Report and continue" to "Ignore".|||

Hi guys,

Thanks a ton for that input. Can you believe it! I am working on the Adventure works sample db and get the same error when processing a simple cube metioned in the tutorial.

I think this option was set to "Ignore" in the CTPs and then it gor switched back in the final release.

Thanks once again! Keep up the good work!!

AS2005 September CTP Errors when Processing Cube

I have a cube which was originally created in the June 2005 CTP.

I have made no changes. I am just attempting to process it in the AS2005 September CTP.

I get random messages like this:

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_PolicyFact, Column: PolicyDimKey, Value: 3135. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Policy Number of Dimension: PolicyA from Database: CDEV15D1, Cube: Cube, Measure Group: Policy Fact, Partition: Policy Fact, Record: 2920.

While trying to process various fact tables. Any ideas? I checked and the key relationships in the source store are all good.

Thanks,

ChrisI had the same problem. The cube processed fine on June CTP but would not process on the September CTP. I discovered my problem was due to the way dimension key errors were handled.

For the "key not found" option on the dimension key errors tab of the processing box, change the default setting from "Report and continue" to "Ignore".|||

Hi guys,

Thanks a ton for that input. Can you believe it! I am working on the Adventure works sample db and get the same error when processing a simple cube metioned in the tutorial.

I think this option was set to "Ignore" in the CTPs and then it gor switched back in the final release.

Thanks once again! Keep up the good work!!

AS2005 September CTP Errors when Processing Cube

I have a cube which was originally created in the June 2005 CTP.

I have made no changes. I am just attempting to process it in the AS2005 September CTP.

I get random messages like this:

Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_PolicyFact, Column: PolicyDimKey, Value: 3135. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Policy Number of Dimension: PolicyA from Database: CDEV15D1, Cube: Cube, Measure Group: Policy Fact, Partition: Policy Fact, Record: 2920.

While trying to process various fact tables. Any ideas? I checked and the key relationships in the source store are all good.

Thanks,

ChrisI had the same problem. The cube processed fine on June CTP but would not process on the September CTP. I discovered my problem was due to the way dimension key errors were handled.

For the "key not found" option on the dimension key errors tab of the processing box, change the default setting from "Report and continue" to "Ignore".|||

Hi guys,

Thanks a ton for that input. Can you believe it! I am working on the Adventure works sample db and get the same error when processing a simple cube metioned in the tutorial.

I think this option was set to "Ignore" in the CTPs and then it gor switched back in the final release.

Thanks once again! Keep up the good work!!

AS 2005: Where are Parallel Period calculations in the Business Intelligence Wizard

I am using the July CTP of SQL Server 2005.

Books Online indicates that the Business Intelligence Wizard in the BI Development Studio supports parallel period calculations. I did not see this class of calculations in the list.

The available calculations were Year to Date, Quarter to Date, Month to Date, Twelve Months to Date, Twelve Month Moving Average, Six Month Moving Average, Three Month Moving Average, Year Over Year Growth, Year Over Year Growth %, Quarter Over Quarter Growth, Quarter Over Quarter Growth %, Month Over Month Growth, Month Over Month Growth %, Day Over Day Growth, Day Over Day Growth %. I would have expected calculations like "Period Prior Year" or "Prior Period"

Is there something special I need to do to make the parallel period calculations available? Or are they just not yet available in the July CTP?Kendal,

When BOL states "Parallel period comparisons", it is referring to the "... Growth" and "... Growth %" calculations that are available. For example, the "Year Over Year Growth" calculation will return the difference between measures for a period in one year compared to the same period in the prior year (whether the period selected is a quarter, month, week, or day).

Let me know if that is not the type of parallel period calculations you are wanting...

Dave Fackler
|||

You have clarified it for me.

I had previously created and used more direct period calculated measures like "Value in prior period" or "Value for same period in prior year". I expected to see those as well. But we can create those on our own based on the provided templates.

Thanks for the response!

Are there updated instructions for the install of CTP and VS beta?

Add me to the walking wounded over the weekend with this beta install.

I have a development laptop that I want it all to reside on.

Installed the VS beta and the April CTP in that order and Client tools were missing.

I removed both, CTP by using the tool that was on the cd and VS by Add/Remove programs.

There are so many threads, it is hard to figure the correct path.

Isn't there a updated install instruction set?

Thanks to all,
Mike
I'm not sure exactly what you are trying to get installed. The steps for the April SQL Server CTP and VS Beta 2 (assuming you install SQL Server Express with VS)are:

Working around the Tools.msi issues with Express:

Scenario 1: Install VS w/ Express First

1) Install VS with Express

2) Go to Add/Remove Programs and remove "SQL Server Tools Express"

3) Install SQL Server Beta SKU with Tools

Scenario 2: Install SQL Server Beta First

1) Install SQL Server Beta w/o Tools

2) Install VS with Express

3) Go to Add/Remove Programs and remove "SQL Server Tools Express"

4) Rerun SQL Server Beta setup and select tools

If you want the latest SQL Server CTP, the June CTP and VS Beta 2 you will need to do the following:
1) Install VS Beta 2 (do not install SQL Express)
2) Uninstall .Net Framework
3) Install SQL Server June CTP

Let me know if I've totally missed your question.

Dan

|||Dan,

I received the new June CTP CD on Tuesday and Installed it before seeing your message today. I'm doing this all on my Laptop running XP Home.

I installed it and I have all my client tools and every thing seems to work in the SQL Server Management.

Seems that it also installed this:
MS Visual Studio 2005
Version 8.0.50215.44
MS .Net framework
Version 2.0.50215

I will need the Express since I'm trying to evaluate a local data cache and synchronization with the server. I am doing this all on one machine.
I did get 2 warnings, one on my machine which does have the minimum requirements, the other was on IIS not being installed.

I was originally shipped the MS VS2005 Team Suite Beta 2, Team Foundation Server and the SQL server 2005 Development Edition April CTP all on CD's.

So to get Express and the rest of VS, what should my plan be?

Thank you,
Mike Davis
|||Hi Mike,

The VS SQL installed on your machine is a shell only release and is used as the home for Business Intelligence Developer Studio.

To install Express I suggest you download the June CTP of Express from http://www.microsoft.com/downloads/details.aspx?FamilyId=1A722B0F-6CCA-4E8B-B6EA-12D9C450ED92&displaylang=en

Do not attempt to install Express from the Visual Studio Beta2 CD - it will fail as different builds (releases) of SQL Server 2005 are not supported side-by-side.

As for Team Foundation Server, I'm not sure if they're supported on the June CTP. But you could go ahead and follow the installation instructions provided but use the June CTP rather than the April CTP.

One word of caution - do not replace the .Net Framework that came with the June CTP with the one that came with the April CTP/VS Beta 2.

Let me know if you have any other questions.

Dan

Are rpts created w/ SQL 2005 CTP compatible with RS 2000?

We have been developing reports for an application using SQL 2005 CTP
version. Turned out that we cannot install it in the production
environment. We can however install SQL 2000 RS. Does anyone know if
reports developed in SQL 2005 CTP can be deployed to SQL 2000 RS? I was
going to try it today but after SP2 to the SQL 2000 RS. The RS 2000 SP2
doesn't run because of the different version in the databases used by RS.
I'd like to know if the reports would work on 2000 or not before spending
more time trying to figure out how to make RS 2000 SP2 work. Thanks a lot
for any help.No, you can do this the other way. RS 2000 reports in RS 2005 but not the
other way.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Bob" <bobatkpmg@.yahoo.com> wrote in message
news:ej%233sQ5pFHA.3104@.TK2MSFTNGP12.phx.gbl...
> We have been developing reports for an application using SQL 2005 CTP
> version. Turned out that we cannot install it in the production
> environment. We can however install SQL 2000 RS. Does anyone know if
> reports developed in SQL 2005 CTP can be deployed to SQL 2000 RS? I was
> going to try it today but after SP2 to the SQL 2000 RS. The RS 2000 SP2
> doesn't run because of the different version in the databases used by RS.
> I'd like to know if the reports would work on 2000 or not before spending
> more time trying to figure out how to make RS 2000 SP2 work. Thanks a lot
> for any help.
>|||I wonder if a bit of XSLT could remedy this problem.|||Yes, you could use an XSLT to change the namespace in the RDL files from
2005/01 to 2003/10. In addition, you need to make sure that you remove all
RS 2005 specific additions to the XSD. Specifically, you have to remove the
InteractiveWidth and InteractiveHeight elements. Furthermore, you cannot use
any new RS 2005 RDL features (e.g. Fixed headers).
-- Robert
This posting is provided "AS IS" with no warranties, and confers no rights.
"Lance" <lancehunt@.gmail.com> wrote in message
news:1124810278.462665.127660@.g43g2000cwa.googlegroups.com...
>I wonder if a bit of XSLT could remedy this problem.
>