OLAP cube - formula length

Hi

dear all,

does anybody know the maximum length for an mdx formula for a calculated member in SSAS?

Kind regards

Frederikm

No hard limit in SSAS 2005.|||

Hi

i find this kind of hard to believe...

I have a formula with over 4000 characters... processing this cube is impossible

the formula is a formula in the form of iif(errorcheck, 0, iif(errorcheck,0... etc

if i use the basic formula without the iif's the cube processes without any problems....

Kind regards

|||There is a syntax error in your formula somewhere, and the error message should give you an idea about location of this error. The syntax error is the real cause of why your cube doesn't deploy, not the length of the formula.|||

Hi

about the max length: is this tied to any service pack version? we are using sp1
also the thing is that there is no error in the formula,
for when we use it in a normal mdx query it works without any problem...
only when in the cube things go wrong

|||The fact that it works inside MDX query means that there is no problem with the length. What is the exact error message you are getting when you are trying to deploy cube with such calculated member ?

OLAP Administrators group in Analysis server

I'm trying to register server in my Analysis Manager. Help says that you should be a member of OLAP Administrators group . Plz tell me where is this group and how can I add members in this group.
Thanks a lot
SandyYou will find this group on the computer with analysis server running on, you can view members and edit the group via windows - administrative tools- computer management-users and user groups|||thanks a lot friend...I was about to lose my hopes...Thanks a lot...I have already done the same.|||Hi There...I did whatever you said...but when I try to register server I'm getting this new error...
"error: '\\server_name\MSOLAPRepository$\msmdrep.mdb' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides."

Could you plz tell me what can be the problem and what could be the solution for the same.
Thanks in Advance
Regards
Sandy|||I have never come across this problem, so this is only guess, the problem could be that when you are registering a remote server, you don't have a permission to access msmdrep repository file which is by default located in Program Files\Microsoft Analysis Services\Bin directory on the server computer, I would try to check whether the file exists and whether you have a permission to access it|||I have put myslef in the OLAP Admin group along with "Everyone", "Administrators" and I still get the following error message: Unable to connect to the registry on the server
(server name) or you are not a memeber of the OLAP
administrators on this server."
I am running this on my local machine and am not trying to connect with another server. I am running sql server 2000. Any ideas?

Landon|||Sandy - I think I came across that problem and it's what mojza is saying. Are you trying to get to the Analysis Manager remotely? If so, try logging into the machine where AM is running.

prdbrat - Your problem sounds like the registry for AS was migrated to SQL Server. If so, make sure you are able to access the OLAP Registry on the SQL Server. I think I had to add my ID to our SQL server before this error went away.|||I know! I know! I had the same problem. Go to your registry under olap server --> delete the remoterepositoryconnectionstring which is a regz_binary.

Than try your analysis manager again to register. It worked for me.

ODBC System DSN Questions

We are running an SBS2000 network with around 40 clients being 60% Windows
2000 Pro and 40% WinXP Pro. We have around 3 member servers (not DC) and one
of the servers is a SQL server running SQL 2000.
A user on the domain has created a dBasev5.7 form that needs an ODBC System
DSN connection from the client to the SQL server in order for his form to be
populated with data. He wanted to roll out the DSNs to all the machines on
the network via Group Policy - I did a bit of digging around in the
Newsgroups and someone suggested this automated way by running a vbs script:
http://www.databasejournal.com/featu...e.php/2238221. Although
this works - we have a slight problem. We have no idea if this is to do with
dBase (it uses 16-bit architecture) but when we roll out the DSNs using the
script the registry gets updated (HKEYLOCAL
MACHINE>SOFTWARE>ODBC>ODBC.INI...) with all the right keys (as if you set it
up manually in Control Panel's ODBC) but we need to go through the System DSN
wizard (to the last page of the wizard) and click the "Test connection"
button in order for the dBase program to access the ODBC database connection.
It seems as if the ODBC System DSN is dead without clicking the "Test
Connection" button.
Questions:
1. Is it a requirement to hit the Test Network Connection button on the
last page of the wizard. I thought that this was only for troubleshooting?
2. It appears that this "Test Connection" button in the wizard posts a
registry key to allow the ODBC SYstem DSN (it has created) to be used. Where
abouts is this registry key?
3. Is there a Group Policy way of doing this? Chances are we may change
settings in the future and may want a server-side script running to update
any changes to clients automatically.
Please help.
THanks,
Skc
I am not usre why this is happening, but I can tell you that the Test
Connection button does not write a registry entry anywhere. It is just used
for testing the connection. Possibly teh script leaves something out that
is necessary and going through the wizard completes the process.
It is possible that an alias to the SQL Server is geing created when the
wizard is accessed. There is a cliconfg tuiltiy that you can use to verify
this.
Run the script on a client machine and then run cliconfg from Start - Run.
Check the alias tab to see if there is an alias to this SQL Server. If not,
then run the Wizard and go through the steps. After it completes go back to
cliconfg and see if there is an alias. In many case the cliconfg utility
will create an alias or a SQL Server when a DSN has been created.
Rand
This posting is provided "as is" with no warranties and confers no rights.

ODBC System DSN Questions

We are running an SBS2000 network with around 40 clients being 60% Windows
2000 Pro and 40% WinXP Pro. We have around 3 member servers (not DC) and on
e
of the servers is a SQL server running SQL 2000.
A user on the domain has created a dBasev5.7 form that needs an ODBC System
DSN connection from the client to the SQL server in order for his form to be
populated with data. He wanted to roll out the DSNs to all the machines on
the network via Group Policy - I did a bit of digging around in the
Newsgroups and someone suggested this automated way by running a vbs script:
http://www.databasejournal.com/feat...le.php/2238221. Although
this works - we have a slight problem. We have no idea if this is to do wit
h
dBase (it uses 16-bit architecture) but when we roll out the DSNs using the
script the registry gets updated (HKEYLOCAL
MACHINE>SOFTWARE>ODBC>ODBC.INI...) with all the right keys (as if you set it
up manually in Control Panel's ODBC) but we need to go through the System DS
N
wizard (to the last page of the wizard) and click the "Test connection"
button in order for the dBase program to access the ODBC database connection
.
It seems as if the ODBC System DSN is dead without clicking the "Test
Connection" button.
Questions:
1. Is it a requirement to hit the Test Network Connection button on the
last page of the wizard. I thought that this was only for troubleshooting?
2. It appears that this "Test Connection" button in the wizard posts a
registry key to allow the ODBC SYstem DSN (it has created) to be used. Wher
e
abouts is this registry key?
3. Is there a Group Policy way of doing this? Chances are we may change
settings in the future and may want a server-side script running to update
any changes to clients automatically.
Please help.
THanks,
SkcI am not usre why this is happening, but I can tell you that the Test
Connection button does not write a registry entry anywhere. It is just used
for testing the connection. Possibly teh script leaves something out that
is necessary and going through the wizard completes the process.
It is possible that an alias to the SQL Server is geing created when the
wizard is accessed. There is a cliconfg tuiltiy that you can use to verify
this.
Run the script on a client machine and then run cliconfg from Start - Run.
Check the alias tab to see if there is an alias to this SQL Server. If not,
then run the Wizard and go through the steps. After it completes go back to
cliconfg and see if there is an alias. In many case the cliconfg utility
will create an alias or a SQL Server when a DSN has been created.
Rand
This posting is provided "as is" with no warranties and confers no rights.