Matadata translations - Editions

Hi,

the link http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

Mentions "Metadata Translations" is a feature of the enterprise edition only - is this true ?

Means if i want to have a dimension name in german and english this is only possible in the Enterprise edition ?
The Sample shows translations and it works in the standard edition - I guess its only a mistake in the documentation - is it ?

HANNES

No it is not a mistake. Usage of translations reserved only for the Enterprise and Developer edition.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||But it works in the Standard edition on my test server - I could deploy translation, but i cannot deplay perspectives . therefore i guess this is wrong in doc.

I use 32 Bit Standard edition with SP1 - and Cummulative Build 2153

Meens this is a bug in SP1 ? and maybe getting removed in further fixes?

MFG
Hannes Mayer|||

If some of the limitations are not enforced by Analysis Server this doesnt mean you can use it in the way it is not intended.

If documentation clearly states you cannot use one of the features in certain edition, you should not. If, say, tomorrow Analysis Server starts enforcing the limitation, you might not be able to see your database.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

master..xp_fixeddrives

I saw an article about monitoring drive usage:
http://www.sqlservercentral.com/columnists/hji/monitoringdiskspaceandsendingalertswithtsql.asp
It relies on the undocumented 'master..xp_fixeddrives' extended procedure in
2000. Now, it's not documented in 2005 either, but I've been reading the
results from a technet search on 'xp_fixeddrives' and it looks like it's in
SQL Server for the long haul.
https://blogs.technet.com/mscom/archive/2007/01/18/keeping-track-of-database-capacity-monitoring-and-planning.aspx
Should I use it?Hi Jay
You could argue that if this is used for an administrative task it is not in
the scope of the critical application functionality and therefore
permissable... but on the other hand any code on a live system could be
deemed as critical!!! Bottom line the choice is up to you, if you do decide
to use it then it should be noted and documented. Any upgrades should
specifically check that this is still available and functions in the same
way. You may want to look at writing your own script such as the perl script
http://support.microsoft.com/default.aspx/kb/318762
John
"Jay" wrote:
> I saw an article about monitoring drive usage:
> http://www.sqlservercentral.com/columnists/hji/monitoringdiskspaceandsendingalertswithtsql.asp
> It relies on the undocumented 'master..xp_fixeddrives' extended procedure in
> 2000. Now, it's not documented in 2005 either, but I've been reading the
> results from a technet search on 'xp_fixeddrives' and it looks like it's in
> SQL Server for the long haul.
> https://blogs.technet.com/mscom/archive/2007/01/18/keeping-track-of-database-capacity-monitoring-and-planning.aspx
> Should I use it?
>
>