A New Internet Library: Add Your Website/Blog or Suggest A Website/Blog to our Free Web Directory http://anil.myfunda.net.

Its very simple, free and SEO Friendly.
Submit Now....

First, an up front apology to Mosha - this is half in jest, half real. MDX is a powerful and useful language, but I find that its very existence has made my life very difficult when it comes to developing a solid Analysis Services solution. That's not to say I don't use it, or endorse it, but I worry greatly about its overall usage.

1) It tempts you by looking like SQL, but once your brought into it you realize how complex it is (if you don't have Mosha's MDX Studio, get it).

2) MDX allows you to do TOO much when it comes to a multi-dimensional structure, without first understanding multi-dimensional concepts. I've seen code that creates filters or subset cubes that overlap or end up cutting out measures implicitly. You have no warning about possibly undermining previous dimensional modeling - that would be a nice addition to see.

3) Along those lines, it enables sloppy dimensional modeling in the first place. "Throw it together, will add in things later". With a multi-dimensional database, it is very important to model it correctly, just like you would a relational structure. Unfortunately there are no Codd/Date rules of normalization, and often very little work done up front understanding the actually relationships and what the data is meant to represent. For example, instead of using a many-to-many cube dimension (what I call the dimesion to measure tie) to represent something like a bill of materials, I often see this done afterwards somehow via MDX calculations and such. Instead of going back to the dimensional modeling, the answer is usually "we can do this in MDX later".

4) Yet another language with its own syntactical oddities - damn you syntax, you will be the death of me!

5) I can't count the number of calculations I've seen in a cube that could have been done before the cube is loaded in the first place. An MDX calculation that does something like PRICE * QUANTITY = TOTAL SALES is just a waste of processing on the cube side. Remember, MDX is post aggregation - so the large the cube, the more dimensions it has and the level of drill down it allows all play a roll in the speed of things.

Those are 5 to start - anyone have anymore?




Source Click Here.

Every year I put out resolutions, but this year is a little different.  I will post my SQL only blog resolutions here, and my personal ones here. Every year I find my ability to put out stuff is limited by my desire for sleep and fun, and this year is no different. So I am going to be realistic this time.I think.

1. Only collaborative works this year.  I am collaborating with Tim Ford (http://ford-it.com/) on the oft mentioned DMV book for red-gate.  I feel it will get done with or without me this time, but I am committed to making it happen.  The MVP book work is mostly done, but there is a good bit more work to do before it goes to print for sure.

2. At least one SQL blog on this site every two weeks or more often.  I have my pillar posts that are in progress, (one is ready for posting in a day or two), and I am going to post some of the DMV stuff along too, most likely.

3. Back on the forums more steady now that the holidays have passed. I try to stick to 3-5 posts a day, even when I am writing, but it can be laborious.  Luckily the talent that is working the forums has greatly improved over the past three years.

4. Bring my back catalog of posts from drsql.spaces.live.com over to sqlblog in cleaned up/updated form, as well as posting them to my website drsql.org for future reference as well.

5. Keeping drsql.org more up to date with stuff I do.

6. Speak at least 3 times this year (user group (nashville.sqlpass.org), Devlink (devlink.net), and PASS, hopefully).

7. Work with PASS on social media to help make them a solid place to go to meet other SQL nerds, even those on other communities.

8. Work on my responsibilities with the Nashville SQL User's group to help us turn a corner to a thriving group.  Right now we have a lot of potential, but need to do a bit more.

9. Read more. One thing about producing content is that it prohibits you from ingesting content from others.

See, realistic.




Source Click Here.

Session submission is now open for SQLBits IV.

 

It will be in Manchester on the Saturday 28th March 2009. 

 

We are planning on having more sessions than before so if you submit a session you will have more chance of being chosen.

 

To submit a session go to http://www.sqlbits.com/information/SessionSubmission.aspx ( you will need to register on the site to be able to submit a session)



-



Source Click Here.

I've submitted a couple of sessions for SQLBits IV 

Submit a session for SQLBits IV

You can see the sessions that have been submitted so far by going here -Submitted Sessions



-



Source Click Here.

When I was a lad and starting out in work an learning about servers and disks I was told of large corporations that regularly replaced storage drives to mitigate against failures.

They would start after x years of buying new storage and start replacing drives. They would, by the time they reached 3 or 4 years have replaced all the drives and be looking to cycle through again.

Things have moved on greatly since I heard this story and wondered if anyone does this, given the proliferation of SANs and often the complete replacement culture I've seen in many places.

The other thing I often find in small places is the lack of spare drives being used in RAID arrays. Whilst I can understand that if, you have spare drives somewhere close, you actively monitor the drives. However in the event of a failure over the weekend a spare can save you in the even you are running a less resilient RAID array or are unlucky.

Do people think that with RAID 10 that the likelihood of getting 2 drive failures in the same mirrored pair is really rare and so don't need spares.

I've created a quick survey if you would like to participate. Its only got two questions so should take you less time that it has for you to read this post.

 

If the survey doesn't appear above Click Here to take survey Cheers

 



-



Source Click Here.

Pop quiz.

Your database is in bulk logged mode. You do a transaction log backup.

Can you restore the log to a point in time between the main backup and the log backup?

Scroll down for the answer

 

 

 

Answer:  It depends

If you don't have any bulk logged operations then you can however the second you have a bulk logged operation you are stuffed, and you have to restore the whole log. So if someone has put a little SELECT INTO statement of a SSIS package that does BULK insert you won't be able to do point in time recovery.

So the lesson learnt is, only switch to BULK logged mode when you don't want to do point in time recovery.

 



-



Source Click Here.

I've submitted a couple of sessions for SQLBits IV 

Submit a session for SQLBits IV

You can see the sessions that have been submitted so far by going here -Submitted Sessions



-

Source Click Here.