|
"Masters of Logic Puzzles II"
After losing the "Spot on the Forehead" contest, the two defeated Puzzle Masters complained that the winner had made a slight pause before raising his hand, thus derailing their deductive reasoning train of thought.
And so the Grand Master vowed to set up a truly fair test to reveal the best logician amongst them. He showed the three men 5 hats - two white and three black.
Then he turned off the lights in the room and put a hat on each Puzzle Master's head. After that the old sage hid the remaining two hats, but before he could turn the lights on, one of the Masters, as chance would have it, the winner of the previous contest, announced the color of his hat. And he was right once again.
What color was his hat?
What could have been his reasoning?
|
Geocaching (pronounced geo-cashing) is a worldwide game of hiding and seeking treasure. A geocacher can place a geocache anywhere in the world, pinpoint its location using GPS technology and then share the geocache's existence and location online. For more, click here.

BSP's NJ office has sent a Geocache to our HQ in Chicago, and you can help get it there!
To Track Progress click Here!
|
|
Join COGNOiSe.com, the largest independent, worldwide FREE IBM Cognos Support Community.
Access our
|
|
| BSP Wishes You Happy Holidays and a Very Happy and Prosperous New Year |
| Greetings!
Welcome to this month's BSP Newsletter. We have a lot of educational content this month, along with some great tips and tricks and other IBM Cognos related information as always! And remember, we enjoy hearing your suggestions regarding the content you'd like to see. Please e-mail us at Newsletter@brightstarpartners.com if you have a topic you'd like to see discussed in future newsletters. |
IBM COGNOS PERFORMANCE 2009 - CHICAGO: A GREAT SUCCESS! | |
BrightStar Partners was proud to be the Gold Sponsor for this years' IBM Cognos Performance 2009 event held in Chicago. We'd like to thank all of our customers who were able to attend the event and stop by at our booth to find out what's new with us! Attended by more than 200 people, Mark Karas, Senior Consultant for BSP presented "Top Ten Tips and Techniques from the Field,"which drew great reviews for the valuable content and information shared with attendees. An outline of the presentation is below:
Top Ten Tips and Techniques From the Field
- Security-driven Columnar Data Display
- Dynamically Nesting Data in a Report
- Express vs. Professional Authoring
- Running Cognos Reports from URLs
- Preserving Top-N Functionality in Drill-downs
- Effective dashboard navigation
- Performance Tuning - Native vs. Cognos SQL
- Automated Promotion of PowerCubes
- Dynamically Showing/Hiding In-report Prompts
- Framework Model Namespaces and Folders
For all those interested in obtaining the presentation as well as the report specifications that accompanied each topic, please click HERE to download the content from the BSP website.
BSP would like to thank you again for making IBM Cognos Performance 2009 - Chicago such a successful event.
|
| BSP ACHIEVES SIGNIFICANT PERFORMANCE IMPROVEMENT FOR CRITICAL EXTRANET APPLICATION |
Recently, BrightStar Partners engaged with one of the world's leading HR consulting and outsourcing companies in a project to review and improve performance in their Cognos 8 environment.
This company built and deployed a critical analytics application to their customers that was not performing up to their requirements. Many reports were taking 5 to 10 minutes to return, with even the initial prompt pages often taking up to 30 seconds.
Without making significant changes to the underlying data mart or the functionality of the reports, BrightStar Partners was charged with significantly improving the performance of these reports by only modifying the Cognos components.
Employing many different techniques, including separating queries to exclude data, implementing date and data limitation logic, and creating separate initial queries with the ability to combine them for drill -hru capabilities, BrightStar Partners was able to reduce the run time of all reports to less than 1 minute, with the average report run time of 40 seconds. Additionally, all prompt pages were reduced to less than 5 seconds.
If you are facing performance challenges in your environment, please contact BrightStar Partners to discuss how a similar engagement can help you achieve the maximum success with your Cognos implementation. |
| IBM COGNOS DEVELPMENT WORKFLOW |
With Change Management, all public content is required to be checked out prior to making modifications. Upon Checkout, the public report becomes locked preventing other users from modifying the content.
Within the checked out copy, Authors can make any number of modifications, saving versions each time they save the content. Once they are satisfied with the changes, the Author can check in the report, unlocking the public version and replacing it with the updated copy. If you are interested in seeing a product demonstration, please visit http://www.bspsoftware.com or reach out to Andy Rachmiel at arachmiel@brightstarpartners.com.
| |
|
IMPLEMENTING COLUMN LEVEL DATA SECURITY |
By Vinay Gupta, Senior Consultant
The technique explained below allows you to apply security to prevent users from seeing certain data.The technique will enforce data security even if the users that are not allowed to see the data are allowed to create their own reports. The technique also prevents breaking of current existing reports and can be enforced on existing reports. Follow the steps below to implement column level data security.
- Create a Security Group in Cognos namespace.
- This security group should have all members that are allowed to see the secured data.
- Modify the definition of the column to be secured. The definition should refer to the security group.
- case
when <Security Group> in (#CSVIdentityNameList()#) then <Column to be secured> else null end
- Publish the package.
- Create a report using the modified column in the layout.
- Run the report as a member of security group.
- You will be able to see the secured data.
- Run the report as a non-member of security group.
- The secured data will be blanked out.
For detailed version of the article with screen shots, click here |
| IBM COGNOS ARTICLES OF INTEREST |
|
In the News...
Version Control and Change Management
Cognos SupportLink Articles of Interest:
|
About Calendars......
- There are different calendars being followed around the world.
- These include :
- Gregorian
- Hebrew
- Islamic
- Indian
- Chinese
All calendars, except the Chinese calendar, have counts of years from initial epochs. Chinese calendar counts the years in cycles.
Count of years from an initial epoch is the most successful way of maintaining a consistent chronology. Whether this epoch is associated with an historical or legendary event, it must be tied to a sequence of recorded historical events.
This is illustrated by the adoption of the birth of Christ as the initial epoch of the Christian calendar. This epoch was established by the sixth-century scholar Dionysius Exiguus.
Given an initial epoch, one must consider how to record preceding dates. Bede, the eighth-century English historian, began the practice of counting years backward from A.D. 1.
In this system, the year A.D. 1 is preceded by the year 1 B.C., without an intervening year 0. Because of the numerical discontinuity, this "historical" system is cumbersome for comparing ancient and modern dates. Today, astronomers use +1 to designate A.D. 1. Then +1 is naturally preceded by year 0, which is preceded by year -1. Since the use of negative numbers developed slowly in Europe, this "astronomical" system of dating was delayed until the eighteenth century, when it was introduced by the astronomer Jacques Cassini (Cassini, 1740).
Even as use of Dionysius' Christian Era became common in ecclesiastical writings of the Middle Ages, traditional dating from regnal years continued in civil use.
In the sixteenth century, Joseph Justus Scaliger tried to resolve the patchwork of historical eras by placing everything on a single system.
Instead of introducing negative year counts, he sought an initial epoch in advance of any historical record. His numerological approach utilized three calendrical cycles: the 28-year solar cycle, the nineteen-year cycle of Golden Numbers, and the fifteen-year indiction cycle. The solar cycle is the period after which weekdays and calendar dates repeat in the Julian calendar. The cycle of Golden Numbers is the period after which moon phases repeat (approximately) on the same calendar dates. The indiction cycle was a Roman tax cycle.
Scaliger could therefore characterize a year by the combination of numbers (S,G,I), where S runs from 1 through 28, G from 1 through 19, and I from 1 through 15. Scaliger noted that a given combination would recur after 7980 (= 28*19*15) years. He called this a Julian Period, because it was based on the Julian calendar year.
For his initial epoch Scaliger chose the year in which S, G, and I were all equal to 1. He knew that the year 1 B.C. was characterized by the number 9 of the solar cycle, by the Golden Number 1, and by the number 3 of the indiction cycle, i.e., (9,1,3). He found that the combination (1,1,1) occurred in 4713 B.C. or, as astronomers now say, -4712. This serves as year 1 of Scaliger's Julian Period.
It was later adopted as the initial epoch for the Julian day numbers.
In the succeeding months, we will read about the interesting details of above mentioned calendars.
Next Month....The Gregorian Calendar..... |
|
|