Encrypt payroll fields

I need to store payroll information (pay rates) in my data warehouse.
I've search on field level encryption and most the stuff i find is for
passwords, I.E. not reversable. I need to protect the payrate field
from dba's and sa's, but I need to allow the authorized users to see
the contents.
Any ideas? Does 2005 handle this?
I don't have a web app, per se, that access's this information. however
I am using Cognos' Report Net.
thanks in advance
RobThe most common solution is to use some kind of encryption library in
your client application or middle-tier, and encrypt/decrpyt the data as
people enter it or retrieve it. In SQL2005, you could use the .NET
crypto libraries within a .NET stored proc, but you can use them
already in a .NET client application regardless of the database.

So it probably depends on what your development environment and
language are. These links might give you some ideas:

http://www.sqlsecurity.com/DesktopDefault.aspx?tabid=22
http://www.aspfaq.com/show.asp?id=2536

Simon|||SQL2005 actually has encryption built-in using either shared key or
certificates (which it can generate). Alternatively, for SQL2000 look
at xp_crypt from http://www.activecrypt.com/.

Empty Measures

Hi,

I have a problem that confused me and I hope anybody can help me.

I have create a Data Warehouse on SQL Server 2005. Then I built a cube with Analysis Services and deployed them. There are no errors during the processing.
But when I start to browse, there are no data in my Measures. My dimensions are correct an have all data from the data warehouse but every measure are empty.
Maybe, is the number of dimensions restricted? I have 88 dimensions and 1 fact table.

I hope anybody understand my description and can help me.

The number of dimensions is not restricted, although 88 is quite a lot simply from the logical model perspective. You might want to look and see if some of these dimensions should really be combined into fewer dimensions. In Analysis Services 2005, it is best to model one dimension per logical business entity and simply include as many attributes and hierarchies as you are interested in using for that logical entity in that dimension. However, the number of dimensions is not the source of you problem.

Some things to check:

When you process the cube, does it report reading fact table rows?|||Hi Matt,

thanks a lot for your answer.

I have check everything you advise me but nothing helped. So I started to delete all relations in my Data Warehouse. Then I started with two dimensions and tested it. Then was everything o.k.
So I started to add each several dimension. At the end I found my mistake. It was a error based on a primary key which consist of two attributes.|||Thank you so much Matt for answering this question. I lost about a day of work trying to figure it out, but then I stumbled upon your answer. I had accidentally commented out the "CALCULATE;" in my calculated measures. Uncommenting it brought back all my measures.

Jason
http://www.stockpickbloggers.com