Showing posts with label regards. Show all posts
Showing posts with label regards. Show all posts

Friday, March 23, 2012

R

When I'm viewing a measure spliced by all the members of a particular dimension, I get an error in regards to the member name's characters.

Here's how the error appears in the different clients -

SQL BI Studio:

TITLE: Microsoft Visual Studio

A list of actions for the selected items cannot be obtained because of the following error.
XML parsing failed at line 12, column 62: Illegal xml character.
.
This error may have occurred because the definition for at least one action is not valid. Verify the definition for each action using the Actions view.

ADDITIONAL INFORMATION:

XML parsing failed at line 12, column 62: Illegal xml character.
. (Microsoft SQL Server 2005 Analysis Services)

Reporting Service's VS query builder complains:
Error:
' ', hexadecimal value 0x08, is an invalid character. Line 1, position 94333. (System.Xml)

In SQL Management Studio:
When expanding the dimension's children, a message yields "Error occured

retrieving child nodes, The server sent an unrecognizable response"

3 free bugs for any SDETs out there :-)
Are there any known work arounds? What's the best way to filter out these characters (and which characters to we need to filter?)

Probably your dimension table contains invalid XML character as part of member name or key. You can go to the attribute which causes this problem and change the bindings on the NameColumn or KeyColumn (depending which one caused the problem) for InvalidXmlCharacters from the default Preserve to Remove or Replace. This will slow down processing of the attribute a little bit, but it should solve the problem.

HTH,

Mosha (http://www.mosha.com/msolap)

Tuesday, March 20, 2012

quistion about sqlserver

hi dear
do you recommend me to install exchange server with sql
server?
please tell me .
best regards
soheila zolfaghari> do you recommend me to install exchange server with sql
> server?
Both servers (Exchange and SQL Server) are memory-intensive, so you should
double check your current or estimated memory needs for your environment and
configure an upper limit for SQL Server manually. They will also compete for
CPU and I/O.
If you plan for previous versions of Exchange and SQL Server, SQL Server 7.0
and Exchange 5.5You must explicitly configure memory usage in SQL Server if
you run both a SQL Server 7.0 and a Microsoft Exchange version 5.5 server on
the same computer. SQL Server will not operate properly if you leave the SQL
Server minimum dynamic memory option set at the default value of 0.
I addition to this, I am not a fan of installing SQL Server together with
anything else, but on a tight budget and in a small environment, there are
no big obstacles for such configuration AFAIK.
sincerely,
--
your Software Submit.NET Team
http://www.softwaresubmit.net
mailto:info@.softwaresubmit.net