denying read rights to a dimension

Hi,

When you give read rights to a cube then the dimension gets read rights by default. Is there a way by which you can grant read rights to certain dimensions of that cube and deny the read rights to certain dimensions of that cube?

thanx.

Changed type Ed Price - MSFTMicrosoft employee Saturday, April 4, 2015 2:06 AM

Reply:

In AS 2005, just create a new Role, and select what the users belonging to that role can see in the Dimension Data tab. If you select the "Deselect All Members" option, then the users of the role won't be able to see any data of that dimension.

In AS 2000, you have to add the dimension to the restricted dimension list when editing the proper role.

Hope this help,

Santi

------------------------------------
Reply:

Thanx. But then in that case I can still see the dimension. However if I dont want to show any of the attributes of a dimension, is it possible to hide the dimension completely..

------------------------------------

XQuery Functions Tutorial

Dear SQL Server XML Fans

There's a new tutorial on how to write XQuery functions written by Dr. Michael Kay. (You can use XQuery functions in both SQL Server 2000 and SQL Server 2005 using 3rd party components like DataDirect XQuery). It's the 4th in a series of XQuery tutorials and covers these topics:

A simple XQuery function example

The function name, arguments, body and result type

Modules and Schemas

Documenting Functions

Using Functions to Mask Schema Complexity

Writing Recursive Queries

Sincerely,
The Stylus Studio Team

Overlap overload, even though I think I love this thing.

SQL 2005 Dev, IIS 5.1, Win XP Pro, .Net Framework 2.0, IE 6

I'm a big MS Access Reporter, now importing reports to SQL Server. When reports are imported from Access, textboxes and labels are not imported at size but rather at size + .1 in. width and height. This is a drag as it causes object overlap errors when built, and total chaos when rendered. (Good luck if you use mozilla!)

Hello Product team! I love this thing. I will keep using it. But whether reports are imported from Access or not, the rendering engine should do something intelligent with overlapping output. As it is, overlapping output throws every object on the page off grid. This is perhaps the limitation of XML and tables?

Keep on coding.

Column Total

Hi,

How can I get the sum of a calculated member in office pivot table. Here is the example

I created a calculated member using

CREATE MEMBER CURRENTCUBE.[MEASURES].PerDay AS ( [Measures].[Total Amount]/[Measures].[Days count]) ;

I display this measure in office pivot table. But the problem is the grand total row is coming row. the values displayed is a divison of total amout / days count. How can I prevent this from happing.

Any suggestions.

Many thanks,

Yash

Changed type Ed Price - MSFTMicrosoft employee Saturday, April 4, 2015 2:06 AM

After Transaction Log Grows, it won't shrink.

The other day I had someone truncate an extremely large transaction log (100GB) but it wouldn't return the space to the OS, not even after a backup and restore operation. There's an interesting bit of trivia around shrinking this file. When the log file is truncated, you may not see all of the space returned to the OS. The reason is the way the data might be spread. Here's the way we think data looks in the log file:

<BeginFile>xxxxxxxx-----------------------------------------------<EndFile>

So when you truncate it and it gets another couple of transactions, it should do this:

But in fact it might look more like this:

So if you truncate the entries and a couple are left it really looks like this:

So when you shrink it, you don't gain any space back because of this file marking. So what do you do?

There are two ways to shrink a large log file, both of which are a bit painful, and not always practical in production. The first is to write enough transactions into the log to "bump" the data all the way to the end. Since that makes it contiguous, when you truncate it you'll get the shrink you're looking for – probably. You can do this by creating a table, adding thousands or millions of rows to it, and then deleting them and the table. Of course this slows down a production system while you do it, and it's difficult to figure the math.

The other way is more problematic in a production system, but works every time. Take a full backup of the database. Follow the process to "detach" the database as described in Books Online. Find the transaction log file for that database (and only that database) and delete it. Then, "attach" the database. The system will automatically build a new, clean log file. Obviously, there are a lot of places you can be careless here, so I recommend this process only for extreme cases.

Reply:

Hi,

have a look here:

http://www.aspfaq.com/show.asp?id=2471

HTH, Jens Suessmeyer.

---
http://www.sqlserver2005.de
---

------------------------------------
Reply:

Good info - but you'll find that the DBCC shrink commands won't work with the TL as I mentioned. It's less a question than some real-world experience - but thanks for the links! I think they will help people to understand how the logs and files are used.

------------------------------------

Welcome!

Welcome to the Windows Server "Longhorn" Server Core Discussion Forum! This is the new home for all Server Core discussions related to Windows Server "Longhorn" and do not fit in any of the other specialized forums. Our aim is to make this a collaborative forum, and that it will be driven by the community more than the team. We want to hear from you and value your experience!

One of the goals of this forum is to provide quality information and reduce the amount of noise. To achieve this, some off-topic posts may be removed, or moved to more appropriate forums. If one of your posts is moved – don't be alarmed – we're trying to get the most appropriate answer in the shortest timeframe. Another key goal is answer questions whenever we can, and attempt to point you to the appropriate resources when we can't. While we cannot commit to answering everything because of development cycles, we will do our best to get you the information as soon as we can.