How can we replace any null cells with a particular value instead?

Hi, all experts here,

Thank you very much for your kind attention.

I am wondering if there is any way to replace all null cells when browsing dimensions dynamically? As when we browse cube data with whatever dimensions hierarchies etc. on rows and columns we always get some null cells which have not intersections between those selected dimension hierarchies on columns and rows at all as we never be able to know where null cells are. Therefore in order to make things better (looking better) like in client tool ProClarity, I want to find a way to replace those null cells with a particular value to make the reports look better?

Is it possible to achieve this in SQL Server 2005 Analysis Services and which can be inherited in its clients as well (e.g. ProClarity)? I am looking forward to hearing from you shortly and thanks again for your help.

With best regards,

Yours sincerely,

Hello Helen! In ProClarity you have two buttons in the dimension tool that will remove empty rows and columns in a table.

Be aware that the NON EMPTY buttons will only remove rows and columns where all the cells a null.

If you enter other values, with the MDX IIF-statement in a calculated member, or format-options(in the Calculations tab in the cube editor) you can hurt query performance.

HTH

Thomas Ivarsson

|||

Hi, Thomas,

Thank you very much for that.

The question to me is, some null cells on some rows where not the whole rows are empty. E.g some cells of those rows are with values, some are not. Therefore it does not look nice. So I want to replace them. But then as you kindly suggested replacing them with other values you have to add calculated members which to some extent hurt performance query. Therefore I think it is better to leave them as they are to the end users.

Thank you very much again for your kind help.

With best regards,

Yours sincerely,

How can I use Sql Express instead of Sql Server 2005 for asp.net providers

Hi all,

Since I activated the aspnet_regsql.exe tool, it has been a bad day - here's why:

Originally I installed VS2005 Pro (without Sql Express) and then Sql Server 2005 Dev. I then started to learn asp.net from the ".NET FRAMEWORK 2.0 Web-Based client Development" Training kit from Micorsoft. I have compiled and run every exercise up till Chapter 9 lesson 2 exercise 1, without the need to start the Sql Server 2005. In exercise 2 I should learn about asp.net profilers and the exercise showed me to use the aspnet_regsql.exe tool if I was using Sql Server 2005 - and so I did, and exercise 2 worked fine after a couple of adjustment in the connection string, because it was configured to use the SQLEXPRESS server by default.

However - in Chapter 9 lesson 3, I should not use asp.net providers, so I shut down the Sql Server 2005, because I don't have that much memory to spend. Now the trouble comes - every website I have made afterwards require that the Sql Server 2005 is running or else I get some errors.

How can I get back to the way it was before I activated the aspnet_regsql.exe, so I don't have to have the Sql Server 2005 running every time I want to make a website using aspx?

Thanks in advance

From your description, it sounds like you need to change the connection strings to use the SQL Express instance instead of the SQL Developer instance.|||

My connection string in both the machine.config and web.config, located in <Win dir>\Microsoft.NET\Framework\v2.0.50727\CONFIG, looks like this:

<connectionStrings>

<add name="LocalSqlServer" connectionString="data source=.\SQLEXPRESS;

Integrated Security=SSPI;AttachDBFilename=|DataDirectory|aspnetdb.mdf;UserInstance=true"

providerName="System.Data.SqlClient" />

</connectionStrings>

And I do not use an web.config at the website level.

I have also tried to reverse the action done by aspnet_regsql, by selecting the "Remove application services information from an existing database" option when starting aspnet_regsql.exe. Then detaching the aspnetdb database in Sql Server 2005 and deleted the aspnetdb files (mdb and log files) from Sql Server 2005 - all with out luck.