Rolling Up Databases for
the Auditor"> So we created Project Data Vault: the ability to say, for a powerful administrator, I want to confine him to just a set of tables or schemas he should have access to. The HR administrator should only see HR schemas, not payroll or anything else. With Data Vault you can split the system into realms and have powerful administrators, but only all-powerful in [given] realms. If they try to get out of those realms, they get blocked.Add-on product, coming out some time by next May. I can see how Data Vault can help with compliance, helping organizations to tell auditors who has access to what information, according to SarbOx rules. What else are customers going to get to help with compliance? Another project, Project Audit Vault, will help with [showing auditors multiple databases]. The auditor wants to see the whole history. He may drill down randomly, to get just samples of information. He cant look at every transaction. But customers will have hundreds of databases in the data center. If you want the auditor to check out hundreds of databases, its a daunting task. Customers want to take audit trails and logswhich, on one database, record all changes to that databaseand take off hundreds of database systems and consolidate them to a data vault. Which is essentially a data warehouse. They want to take auditing information off all these systems, and consolidate it on one system so they can check out whats going on in all these systems. It helps to deal with SarbOx issues. Its interesting for North American customers or anybody who wants to do business in the United States. What else is hot in R2? Coming up real soonby Mayis the 10g R2 version of grid control, our new enterprise management capability. Instead of an administrator doing one system, he can manage all systems across the grid. Also, CPUs [Critical Patch Updates]: A customer who has a big data center might want to very rapidly roll out these CPUs to all their production systems. That can be expensive, time-consuming. So with R2 we have nice automation for that. The grid control console has a link to the support site, to MetaLink. Grid control automatically pulls down the alert to the site and notifies the customer. Grid control says, You have 500 systems in the data center. As far as I can tell, youve applied the CPU to just three. Can I roll out the patch to all the others? The admin can click on systems to apply the patch, or he can say, Take these steps first; say, I want this system down on Saturday at 2 a.m., and send notification to users before taking it down. And it will restart automatically for you, too. Thats something that in the past has been time consuming. Whats the main goal behind R2? For R2 to be very robust. In [Chuck Rozwats] keynote well show high-performance implementation of a basic sorting algorithm. Customers sort millions of times a day. If you make that run faster, you can make a lot of stuff run faster in the data center. In R2 we looked at the chips in the marketplace and built this new sorting algorithm that makes it run much faster on new chips. Were talking huge performance increases: up to 5 times faster for sorting. We think this is the kind of thing from which our customers will really benefit. They can take batch jobs that took 2 hours to run and cut them down to 30 minutes. Check out eWEEK.coms for the latest database news, reviews and analysis.
Is this an add-on product, or is it included in R2?