Sometimes we need to check the existence of a table in a script or scheduled task to record events of errors, first executions etc ... Let us take an example, a package of integration services that we tend to distribute or run there where we go and that leaves traces in a custom table that is not the default for loading logs. We could always include a performance task or sql script, run right or wrong, is the first to run on the package and then continue. Being purists this just is not quite "neat"
CREATE TABLE LogsEtl (Execution int PRIMARY KEY, Package varchar (50), Date datetime); GO
In the first run the output is correct but fail after creating the table.This can substitute vision consulting sys.objects , where there is a record for each object in the database, and verify the existence of the table before creating it. The visibility of the metadata is limited to securables owned by the user or on which the user has any permissions.
This series of articles was originally published on the website of Business Intelligence for @ bifacil . Given the good reception of this series on how to build a data warehouse , I decided to publish it also in my Blog DATAPRIX. Hope you like it.
The origin of this series is a very interesting article by Ralph Kimball (Any clueless who do not know?) which details the 12 most common mistakes in building a data warehouse.
This is an excellent article .Every time I have committed any of these errors, I had to rectify soon. Not worth the shortcuts to do things right from the beginning.
The twelve most common mistakes in building a data warehouse are:
- Error 12: Include text attributes in a fact table, if done with the intention of filtering or croup.
SSAS: Removing the system administrator user administrative access to our Analysis Services instance
Security in Analysis Services security is based on Windows itself. Users are authenticated using local Windows accounts (server) or domain and may have rights according to the roles to which they belong. What does this mean? By decree and if not we change the configuration of our SSAS instance users who belong to the Administrators role of SO as Administrators also can enter the instance. To change this behavior and limit the administration of SSAS to users who have marked as such we must change the value of the property Security \ BuiltinAdminsAreServerAdmins and set it to false. But be careful in doing so, we will not run out of managers, we must first make sure we have another account in the list of SSAS administrators.
To access the properties of the instance we connect as an administrator and do the right button click on the name of it. In general we see and change the value there.
For a list of current administrators of the department which have been added explicitly in the same place, but we can certainly reference point.
With version 9.7 of DB2 LUW, IBM makes a nod to all Oracle DBAs, much more numerous in the DB2 market.
For this reason, in version 9.7 has introduced Oracle compatibility modes that let you perform tasks in DB2 with the ease and knowledge that all Oracle DBAs have. However, it is important to know the translation of terminology between Oracle and DB2 if you intend to get into the DB2 world.
In this first article, I relate a number of items from which this introduction is simple and can be read easily DB2 documentation. Including general terminology, updates, utilities, and views.
Oracle does not normally expect to find in SMEs but rather in large enterprises. This makes us have to put batteries in terms of security, not to implement a simple configuration but make a good and detailed study.
What better than a checklist to help to put a good setup and we are not passing anything. That is why I attached a pdf format and is divided in four sections: Reinforcement, Security Updates, default passwords and default ports used by Oracle.
Hope you like ..
Well, after the draw for two tickets for a 0 º Forum of Business Intelligence , which have won the users BI easier and hminguet Pau (BI easy) confirmed he will attend, and Hector (hminguet) still is thinking .
For my part I also confirm my attendance at this important event BI, and I will be there available to anyra want to say hello 'physically'.
See you on Wednesday in Madrid!
We have created a space Dataprix which we call Lab, accessible from the domain labs.dataprix.com , where we operate online experiments and demonstrations of products.
Start the experiment, in beta, allowing online access to the virtual image and Mariano Dario Pentaho of eglue Group . A try and we will say what that is behaves. We hope in future to be updated version of Pentaho and go to expand the data, reports and dashboards available, but what we have now is enough to prove how this Open Source BI server.And if anyone wants to tinker more simply download the virtual image, with all pre-configured development environment.
The user pre-configured in the demo have permission to create new reports. To ensure the quality and usefulness of it from time to time review the new reports and let us just look more interesting.
Hi, I am very pleased to announce that version 2.0 is ready Hephaestus: Data Warehousing: Concepts Research and Systematization - Hephaestus: Methodology for Building a Data Warehouse. "
- Query Manager -> Drill-through.
- Data Area.
- Surrogate Keys.
- Slowly Changing Dimensions.
- Degenerate dimension.
- Size Clustering.
Today we all know the email as one of the most widely used marketing tools, but most. We are tired of receiving hundreds of emails every day trying to convince us to buy any product that we promise the sky and pretend to be the solution to all our problems. But what makes us an email to open or not, and does do some campaigns succeed and others fail? Where is the difference to get our customer reach or stay in the bin of your email program?
Today we all know the email as one of the most widely used marketing tools, but most. We are tired of receiving hundreds of emails every day trying to convince us to buy any product that we promise the sky and pretend to be the solution to all our problems.But what makes us an email to open or not, and does do some campaigns succeed and others fail? Where is the difference to get our customer reach or stay in the bin of your email program?
We will try to draw some conclusions about what a difference from other campaigns.
As I Zun Tzu: "The battles are won before they start." With email is exactly the same, once given to the submit button, all bets are off and if we have not hecho our job, our campaign will not work.