A customer reached out to me with some questions on our Business Data Integrator Adapter. This is an adapter (Integration module) that is designed to pull data from a database and bring it into BSM and/or CMDB. He was using the IDE (think of a drag and drop designer to define what the database integration should do) and had a question regarding how he could have the result set produce some different results in a self defined column based on the data returned. I think we discussed some type of case statement or something. Anyways, the email was titled "Data base question". I typically ignore typo's, bad grammer, etc, because I produce so much of that, I'm in no position to correct people :)
I remembered years ago I was working for a government contractor, we were helping the government produce an RFP. There was a huge debate at the time if database was two words or one word. I put my foot down that it was one word. Unfortunately, the dictionary didn't back up my position. I gave up, the RFP went out with over 20 references to "data base".
Due to this email, I decided to check an online dictionary and of course, it does show up now, one of the definitions made me smile though. In order to not plagerize, it said something like a database is a colleciton of data, it also spoke to this data being retreived by a computer with the words "ease" and "speed". Ok, it's probably not funny. I've been in support roles in the past with a few companies and over the years, complaints about the speed/performance of the database is a common one. The speed of the database is one of those areas that just doesn't happen auto-magically because you decided to move your spreadsheet into a database.
There are so many considerations that have to be taken into account when you leverage database technologies. Even with out of box products that have sizing, configuration, architectural recommendations, "tuning" of the database typically ends up to being something that has to be done on an ongoing basis. Sure there are some standard settings or ways to organize the data, probably specific configuration settings, but as the data grows, there are some techniques that can be implemented to improve performance.
There is an endless list of things that can be done to address performance related issues with a database, between isolating highly used tables and/or indexes to faster disk access areas, to contolling how often indexes split, setting up views, stored procedures, etc. The list goes on and on, there are also specific steps that can be taken with each vendors database. Ok, I'll reel it back in, the point of the blog was around data base, data-base, database... which one? Is it differnt regionly? (or... do you have any others?)
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.