data = energy

Have you ever wondered what data is exactly?

What if data = energy?

Data flows in and out of the database.

Data, when stored in the database is 'Potential' energy.

It's up to the report writer to release this 'Kinetic' energy back into the universe.

I suppose data can not be created nor destroyed, it just changes location, or shifts.

So think about all the bundles of energy stored in those Terabyte database.

Just sitting there, stored energy, waiting to be consumed/released.

Kind of a 'powerful' concept, yes?


SQL Community

SQL Saturday #62 - January 2011 - Tampa -

Pre-con B: End-to-End Business Intelligence
Presenter: Stacia Misner

Although I've programmed in SQL Server for close to a decade, this was the first opportunity to get introduced to the SQL community.

Attending that free conference, I was introduced to many SQL people from around the country. 

Attending Stacia Misner's pre conference, I learned how much there is to learn in the Microsoft BI stack. 

I starting attending the Tampa Bay SQL Server BI User Group.

And have been to the SQL-Saturday in Orlando and again in Tampa since.

The people in the SQL community are really awesome.

They are on Twitter, LinkedIn and there always seems to be a free webinar going on.

The community really opens themselves up and takes pride in dispersing information on a regular basis.

The amount of literature on the web and demos and tutorials and blogs is quite incredible.

I've programmed in Crystal Reports since 1996 and let me tell you, at that time there basically was zero information on getting started.  I had to learn from scratch with no community.

Then onto VB, .net, Java, Oracle and now back to Microsoft BI full time.

I'd say the community has helped me to become a better programmer, to advance my skill set and increase my career opportunities.

It's nothing like I've ever seen.  Smart people willing to share what they know.

I'm glad I found the SQL Community.


2011 Personal Achievements

2011 Personal Achievements:

2011 was a good year.

I switched jobs in January.

The position I accepted actually turned out to be a Supervisor position, who knew?

I adapted nicely to the new role.

I'm fully immersed in Microsoft SSRS.

I attended 3 SQL Saturdays.

Met a bunch of new people.

And learned a lot of new Advanced BI concepts.

What are my goals for 2012?

I'd like to be working actively in Microsoft Advanced BI.

I'd like my salary to rise to match my skill set.

I'd like to be swimming in our new in ground pool.

I'd like to take at least one vacation to the Georgia Mountains, possibly two.

I'd like to continue working my part time contracts.

I'd like to continue to learn new skills.

I'd like to meet new people in the IT field.

I'd like to stay healthy, play some tennis and eat healthy.

I'd like to bring closure to things that went wrong earlier in life.

It's never too late for a new start.

And so it goes!


Social Media - Twitter

Social Media - Twitter is the next best thing since sliced bread.

The reason for it's popularity, in my opinion, is three fold.

Networking: The ability to communicate with a vast number of people and find people of similar interest in a matter of seconds is truly remarkable.  By connecting on Twitter, you can follow the tweets and reply, re-tweet, view their attached URL / pics and not only network but learn in the process.

Information Dissemination: the use of hash tags allows your Tweet to go across the planet instantaneously.  Image in the power behind that.  This phenomenon was virtually impossible just a few years ago.  Imagine what will be available in a few more years.

Problem Solving: Recently I commented on Twitter about Bright House messing up my bill and charging me a $5 fee.  Someone from Bright House immediately contacted me, backed out the $5 fee, and then I was able to ask questions about product and actually upgraded my account.  The days of IVR automation hell may be over with the quickness and responsiveness of the future customer service.

The main thing I hear from the people who don't 'get it' is 'why do I want to tell the world what I'm eating for lunch'?

Twitter is much more powerful than that.

It's the new 'community'.

Team Lead Role

What does a Team Lead do every day?

Well, for one thing, the role of a Team Lead is diverse.

The main responsibility is to keep up with the incoming report request queue.

By that, one must utilize the resources available to complete the reports in a timely manor.

The main source of reports comes from the Ticketing System.

There are also email requests from various people/departments.

The Manager or CIO can assign reports or Directors from various departments

The state can request reports.

There are ongoing project that require reports.

So there are a variety of ways a report can get requested.

When a report gets requested outside the ticketing system, the Team Lead usually enters a ticket request and assigns it.

So there is a lot of communication outside the IT department.

With a variety of different customers.

Most communication is done via email, some phone calls and the usual amount of face to face meetings.

There is also the administration functions that must be handled.

Workers sometime call in sick, or late for work so signatures are required on time sheets every two weeks.

Approving vacation is also required by verifying the necessary staff is available.

Then there's the Annual Performance Evaluations.

One more thing that should be mentioned is giving 'positive feedback' to workers whenever they do a good job.

I like to commend people for doing a good job, especially to the higher ups.

Which makes them feel good and enforces the type of behavior that's expected.

Also, when work is not up to par, there are mentoring sessions.

Which leads into training.

And I'm a firm believer that a worker must have the necessary tools to do their jobs.

And, in my case, writing reports is also expected.

I tend to take some of the more complex reports, some reports that can be done quickly or when a report requester is high up in the food chain.

The key is to determine the workers skill set and assign the work appropriately.

The stronger developers get the more complex reports and vice verse.

We also have Team Lead meetings with our Manager where we discuss current projects, up coming projects, and a variety of other topics within the department.

There is a lot of responsibility in being a Team Lead.

It's not a bad position, as long as you still get to write code.

The one thing I find interesting is seeing the work environment from the other side.

No longer do I have the luxury of complaining how bad things are.

Now I'm responsible for getting the job done with the resources available.

And so it goes!


SSIS Package to Excel Dynamic File Name

Well, on my part time job, I was requested to create an SSIS package to dynamically create a TEXT file with the file name to include the date run.

Sure enough, I did this.

Then the user changed the export file type from Text to Excel.

I thought this was a no brainer.

Until I got into the guts of the code.

I found this link as an example:


It ran in development and all was well.

Until the next day, the package would not compile.

Why?  Because the file was not already created with the next day's date.

So I read and re-read the article above and it just didn't make sense.

Until, poof, I figured it out.

You have to create the Execute SQL Script at the beginning of the package, referencing the Excel Destination, in order to create the spreadsheet in advance.

I then deleted all the Excel files used in testing, re-ran the package, and sure enough the new Excel file with correct file name appears.

And so it goes!


Reporting Career

So what is it that I do for a living, I do 'Reporting'.

I have 15+ years experience in 'Reporting'.

And a year as Supervisor / Team Lead.

A lot of it was Crystal Reports, some Actuate, some Jasper, and finally Microsoft SSRS.

I used to program in VB, then .net.

Then some Java & JSP.

However, that was a few years ago and I don't write any .net / Java at this time.

And I don't work with SharePoint.

I'm not a DBA.

I don't really do Business Intelligence with OLAP or Data Warehousing.

I just do Reports.

And I like it.

Some call it 'Simple' or 'Easy'.

Most developers shy away from such lowly aspirations.

I guess the way things are now a days, its getting difficult to find jobs that do 'just reporting'.

Everyone wants you to do something else as your main job and also expect you to know reporting in addition.

Like I've been saying for years, there is a 'Huge' demand for getting the data out of the database, into a report, to be consumed by the customer.

This role may not win the award for most glamorous, most highly paid or Rock Star material, but it's a niche that's been the majority of my career.

And I'm proud of it!


IT Job Titles

What's the difference between Software Engineer III, Software Developer, Programmer Specialist, Principle Developer, Lead Developer, Application Developer, Business Process Engineer, Senior Software Engineer/Developer/Specialist, etc. etc. etc.

You get the point.

Seems like some standardization is in order.

I have no idea who does what, the differences / similarities, skill level, job functions, etc.

How did IT Job Descriptions get so fragmented.

One company has one naming convention, another company has completely different one.

Who's driving this bus?  Or is it a free for all?

When I watch baseball, I know what a '3rd baseman' does.  I know what the position entails, what skills are required, where on the field the position is, etc.

I have no idea what a Software Engineer III does.

And I think that's a problem.

What do you think?

Proof is in the Reports

You can create an application that meets the customers expectation and still have a failed project.

Because, as most of us in IT know, reporting is the last thought of every project.

So by the time the Reporting Department is handed a list of reports to create, that's when the potential design flaws appear.

Let's say you have to tie the application data to another data source / database.

Yet the app developers did not think through their design when creating the database to allow it to interact with other data.

So there's no 'direct link' between systems.

And that is what we call a 'design failure'.

Who created it?  The project manager, the business analyst, the developers, the users, the entire team.

Why, because they did not include the reporting department in their analysis.

Well guess what, the application is already in production

A little late to be redesigning tables, do you think?

Well, in our case, we have to meet State mandated reporting requirements.

So what does that mean, that means the software vendor needs to modify their application, ASAP.

So in a sense, the reporting department is little bit like QA.

If the biz rules don't jive with reporting, the app ain't gonna fly.

Because now the software needs modification.

Which takes time and money.

I really think Reporting should be included in a lot of application design meetings so these things don't happen downstream when time is limited.

It's always easier to do things right the first time.

And there you have it.



Quick question, have you ever enjoyed writing documentation?

Sure anyone can take a few screen shots, throw down some sentences describing the screen, and presented that as documentation.

I know I've done that in the past.

Here's another question, do you document your code as you go?

I always do.  With my initials, description of what the code is doing and anything else that might be relevant.

Working for Florida Power company, the senior Visual Basic developer mentored us lowly coders with surprise code review.  If we did not have comments, he would dig into us until we wished we never became programmers.

One thing is for sure, he knew how to code.  He was a master programmer.  And I learned an enormous amount of coding practices from him including 'documenting the code as you go!'.

He also got me to become the Visual Source Safe admin which was a nice boost for a junior programmer at the time.

He also helped us get to go to VBITS - which was held in Orlando - where the expert Visual Basic programmers got together to discuss code, watch demo's, etc.

I found that I learned more from speaking to people between and during the sessions out in the halls than I learned from listening to the speakers.

One thing I'll never forget is the description of building a house, then the customer asks where the basement is.  That's a classic programming issue, especially in the world of Rapid Application Development which VB 4,5&6 was known for.

Anyway, always remember to sometimes document your code!

Business Knowledge

How important is 'Business Knowledge'?

Can you perform your job based solely on understanding the code.

I have always prided myself on never learning any biz logic I've ever worked for.

The Power Company, Medical Timekeeping, Credit Card Processing, Telecommunications, Banking Insurance, Healthcare and Government.

Sad fact but true.

For some reason I understand just enough to code the application and / or reports.

All the logic is in the code and some of its even documented.

This is probably the first job where I've had to learn the business - the School Board is quite complex.

Not only do I have to understand the logic to write reports, but sometimes one of my workers has business logic questions they ask me and I'm expected to know the answers.

Also, when speaking to the customer's it helps to know a little something about what they are talking about.

In summary,  Biz Knowledge is good to know, will help you keep your full time job during crunch time, although many people have done their job successfully without fully understanding all the intricacies behind an app/report.

So there you have it.


SSRS - Side Item

If you look on the Indeed website and enter 'SSRS', several jobs pop up, however, almost none are for SSRS.

You have Sharepoint, DBA, Analyst, C# developer, Data Architect, ETL Developer.

What the heck is that all about?

Why is it that doing straight reporting in SSRS isn't a stand alone position?

If programming were a meal, SSRS is no longer the main course - it's a side item.

That just doesn't seem right.



Well, my part time job emailed me late Friday with an amendment to the original contract - they want to extend me to March 31, 2012.

That's good.

From the looks of it, they have 40+ SSRS reports to convert to the data warehouse tables instead of the raw data tables.

I imagine mapping out the new fields to take some time and estimating out each of the steps.

This go around they have me estimate all my work for the entire month.  Then it gets approved, then I do the work.

I submit my invoice beginning of the following month, which they have 10 days to approved.

Then they have 30 days from then to issue the check.

Whew, quite a long process.

But a check is a check, which is good as cash, which the bank is glad to deposit.

I worked for the same company all last year.

I had to stop when the School went on Summer school hours - 4 ten hour days - which I took the bus - which meant I couldn't get the necessary hours in -

They called me late September to do some more work which I gladly accepted.

I did a contract before that one, for an international company, which I found on Craigslist.

They paid quite low, but I got some good experience with SSRS and T-SQL consolidating 5 country databases into a single repository nightly.

Before that, I did a few websites for a tennis/golf club.

Before that I had a friend who owned a software company and I helped write some VB6 code which checked files in and out of Visual Source Safe through COM+ and DLLs.

Before that I did some ASP web development for a travel website.

Before that I did some volunteer work for a local computer club.

I guess I started my side biz in 2000, which is when I signed the paperwork with the attorney to have the name Bloom Consulting as Sole Proprietor and got a federal tax id.

Eventually, my goal would be to incorporate and do Independent Contracting full time.

And so we dream.


What is it you do here

What is it you do here?

What value do you add to this organization?

Well, I'm responsible for the Reporting Services department consisting of two report developers.

We are basically a production line of report requests.

We receive incoming request via the ticketing system to fix bugs, create new reports as well as projects.

Our job is to find the most efficient way of extracting the data into a readable report on the web in Report Manager for consumption to the internal users within the School Board.

I meet with customer from time to time to discuss report requests.

I give status updates to my boss.

It's basically a good job with a lot of responsibility.

I did a recent search the other day and the salary range for this position in this area was about $25k higher than what I'm currently earning.

If it were not for my part time job, I would have to really assess what my future career plans are.

Hopefully, down the road, someone will have a need for a person with team lead skills, who knows how to create reports, in SSRS & Crystal Reports & Actuate, who can program in .net C# and VB as well as JAVA and Oracle.

I think I could earn more money in any one of these individual skill sets than what I'm currently earning.

I look back on my career and realize I have made some poor decisions regarding my career.

I will seek to rectify that going forward.

That's about it for now.


Report Viewer BI Solution

In all the time I've worked with SSRS, I've never seen the report displayed on the web in ASPX.net embedded in Report Viewer.

Sure, I played around with the Report Viewer in c#.net and got the report to render locally as an .rdlc.

However, I stopped developing with it after I was blocked with sub-reports.

I was not able to render a report with 4 sub reports after researching the web.

This week, I saw a fully functioning BI solution developed in SSRS using embedded Report Viewer reports.

Actually, it was a great application with tons of graphs and hyperlinks.

Under the hood, the app was storing 'session' variables by passing the parameters from page to page, similar to 'session' web apps.

Also, you could drill down several layers and view graphs along the way along with detailed info.

When the user see's something that stands out, he/she can drill down further to see the most granular level of detail which comprises the scorecard at the higher level.

And that my friends, is what I think true BI is.

I never contemplated a BI solutions in SSRS without using cubes, which contained executive dashboards with fancy colors, with hyperlinks to drill down to the finest level and back up.

I was definitely impressed.

I want my D-A-T-A

With all the hype lately about Dashboards, Scorecards, Big Data, Non Structured Data, I continue to see a trend less talked about.

I still see customers that want nothing more than to 'see' their data.

That's it.

To be more specific, they already have access to their data. In bits and pieces. And it takes days/weeks to export and consolidate.

What they want is a pre-created report, bringing in all relevant information, viewable on the web, with changeable parameters, exportable to PDF or Excel.

That's it.

They are not even aware of all the hoopla surrounding the Business Intelligence world.

For these types of customers, being a one eyed person in the land of the blind is what it's all about.

If you can get them their data, they are ecstatic.

I think this scenario is typical in a lot of organizations - people just want the access to their data. For whatever reason.

In the 80's it was 'I want my MTV'.

In the 2010's, it's 'I want my D-A-T-A'.



As anyone working in the IT field knows, work can be exhausting.

It can drain you physically, mentally and emotionally.

That is why they invented vacations.

This week my wife and I spent a week in the Georgia Mountains.

We rented a cabin in Blue Ridge, Ga. We usually visit this area twice a year for the past five years.

I'd have to say this was out best vacation yet.

The cabin was secluded, close to a creek, close to town, very spacious, plenty of amenities, clean, screened in patio, new grill and best of all, it had a fenced in yard for the dogs.

That meant that I did not have to wake up at 6am to walk the dogs on leashes.

The wife woke up and opened the screened patio door and the dogs went a wandering.

This was a vacation in itself.

We then awoke, had coffee, showered and drove over to the Waffle house each day to enjoy an egg and cheese biscuit.

Then we journeyed to one of the State Parks, Fort Mountain and Vogel as well as Blairsville, Hiawasi and Ellijay.

We mostly ate out fast food for lunch and cooked on the gas bbq each night.

At night we rested, read books and spent some quiet time doing nothing.

Tomorrow we head back to Florida - long drive - then we have Friday, Saturday and Sunday to unwind from vacation.

Not sure if we'll be back in April. Will have to see how things look at that time.

One peculiar thing to mention. Every time we've been to this area the people have always been so friendly. Southern hospitality I suppose.

Not this time. The locals were very unpleasant and seemed to cater to the locals.

Perhaps the down economy has dried up their customer base and they now focus on the repeat customers.

We were kind of disappointed about this as we usually enjoy spending time with the locals.

Either way, the dogs had a wonderful time as did my wife and me.


Microsoft Access

Seems all the rage lately surrounds Microsoft SQL Server Denali / 2012.

Whatever happened to Microsoft Access.

Seems I have worked with Access for a long time now.

The basic premise is awesome.

You have a database.

Can import tables from Oracle/SQL Server either linked or imported.

You have ability to create forms.

You can utilize the built in VBA/Modules.

You can definitely create reports.

It has somewhat built in security although easy to crack the passwords.

It's small and can be uploaded to websites easily and easy implementation to store data for online apps.

Some of the limitations:

Size - constantly have to shrink the db.


In order to maintain the db you have to work on the pc - there is no built in 'Web Interface'.

I was thinking they could build one and use the product to compete with MySQL by giving it away for free --> isn't that how it works, give a product away to crush the competition?

Anyway, I believe it's a fine application that bundles with Office.

I have not researched the 360 version or if it even exists.

Maybe someone can clue me in on that.

From what I've seen with the latest version of SQL Server so far, it's just an amazing product.

Perhaps Microsoft can leverage their ancient solid application called 'Access' too.


What is it you do here?

What ever happens to all that information entered into the system every day?

It's stored in one of the database repository's as 'raw data'.

The Reporting Services team is tasked with converting 'raw data' into 'information'.

That 'information' allows internal and external customer's to manage their business and make decisions.

Reporting Services does that by creating reports which reside on the web to catch
exceptions and help the internal business units run smoothly.

So Reporting Services takes the raw data, converts it to information, in the form of files & reports, for client consumption, to allow the Customers to manage their
business and make timely and accurate decisions.


3/4 through 2011

This year is about 3/4 over. Or 1/4 to go.

Either way you slice it, it's been a pretty good year thus far.

I changed employers in January, from one government agency (the County) to another (the School Board).

What a world of difference.

Rigid, out-dated technology, no authority, strict environment TO relaxed, somewhat current technology, supervisor position in a good atmosphere.

I was almost running out of things to do at the County while transitioning from Java to Oracle / SAP (XCelcius) BI position.

The School Board is a fast pace environment with endless requests.

I enjoy the challenges that are associated with supervising a team of two full time report developers and a contractor.

And interacting with peer supervisors.

And meeting with all the friendly customers.

And writing reports.

Just today though, I was reminiscent of the programming days.

I guess I still miss writing code for web applications and such in Java/JSP/VB.net.

I got my start in Crystal Reports, Oracle and Visual Basic so I always had the three main things covered: getting data into the db and getting it back out in an application.

I attended the SQL Saturday in Tampa in the beginning of the year and then again last month in Orlando - both were excellent events. There's another one next month Nov. 5 in Tampa I plan to attend as well.

I managed to conquer my fear of 'true' BI and dabbled a bit in the new SQl-Server Denali.

I got some SSAS, MDX, Power Pivot experience and hope to finish up with some Share Point.

However on my job I believe we plan to purchase a pre-built data warehouse in Cognos which we could query in SQL from SSRS which would be nice.

And if they ever replace the AS400 they are going to have a lot of new reports to manage and create.

Looking into a crystal ball, I would say that creating reports seems to be in my future.

Also, I had stopped my part time job in June because we had to work 10 hour days in the summer.

I was pleasantly surprise to receive a phone call from my old boss asking me to pick up where we left off.

So I started back part time in early October and it should last until the end of the year - with the possibility of extension. I was extended several times last years so I'm hoping to continue the trend.

My family is heading to Georgia mountains next week to rent a cabin - can't wait to see the leaf color changes and cooler temps.

I have to say this. People raz government workers for being lazy, making huge amounts of money and sucking the country dry.

Well, I've been on both sides of the fence, Public and Private jobs.

I have to say that some of it is true, there are some people who work for the gov't who haven't seen a full days work - ever. But those people are slowly being weeded out. And as far as making lots of money, uh, I don't think so. I'm about $20k underpaid at the moment, in this market. Moving to another market, I'd say closer to $30-40k underpaid.

That's why I have the p/t job though.

Anyway, my skills are slowly improving, I hope. I'm fully into Microsoft reporting at the moment, which is where I wanted to be this time last year.

Overall, things are going well.

I look forward to closing out the year with some time off during the holidays and will see what develops next year.

Thanks for reading the articles on my blog - I write quite often and have no idea who actually reads these things.



Microsoft SQL-Server Integration Services is not a new product.

It goes back to the original DTS packages of years ago.

I wrote DTS packages and felt comfortable in that environment.

So when writing/debugging SSIS packages, I have an understanding of what I'm doing.

However, if you didn't write the package, and asked to debug it, it is not an easy task.

On first glance, the package seems overly complex.

However by breaking each task down to simpler units, it's not difficult to understand.

In the 2008 r2 version, they have some new features.

However looking at the SQL code beneath seems straight forward.

What I did to troubleshoot is to number each task and write a brief description.

Next, copied the SQL to Transact SQL editor to view what's going on.

However, I can not run the package because it updates production tables and such.

Once you have a birds of view, as well as look under the hood, the problem presents itself.

In my opinion, SSIS is another animal when it comes to programming.

It's not your typical Java or .net app where you can step through the code line by line.

It's a bit fragmented.

But not impossible.

I still prefer to troubleshoot production problems of someone else code rather than write the code from scratch.

Guess that makes me a "maintenance" coder.

Kind of a niche.

Oh well, could be worse I suppose.

SSIS is good for doing specific tasks.


Create Insert Statements from SQL-Server table LINK

Found this link to a Stored Procedure that will create a list of "Insert" statements for a particular table.

Works great!

- Create Insert Statements from SQL-Server table -


#SQLSat85 - Orlando

Just got back from #SQLSat85 in Orlando -

I thought it was great!

Started off with Bill Pearson's MDX class - great presenter!!

After that, same room, @Adam_Jorgensen presented from "Zero to Cube" - learned some good stuff!!

Then chatted with Bill for awhile about the industry and future of BI.

Next was lunch - some good B-B-Q.

Chatted with some of the Tampa Bay BI Chapter posse.

Then sat in a BI class -

Same room, listed to Kyle Walker present "SSRS Subscriptions" - good information as well as SSIS demo on how to email multiple PDF files using Pragmatic Works custom control for SSIS.

Last, same room, Bill gave a good presentation on DAX - a lot of smart people in the room including an Access MVP who asked some good questions.

Had to get back to Tampa Bay - left around 4pm - got home 6pm in time for dinner - and now a cigar!

Thanks to the organizer for a great event all around - my 2nd SQL Sat so far - next one is in Tampa Nov. 5 BI -

Can't wait!


Learning Microsoft BI

So you are finally out of school, that learning was such a drag.

Well, you could get a job as a line operator in a production plant - and you'll most likely never have to learn again if that's what you choose.

However, if you chose the profession of IT worker, chances are you'll never stop learning.

I've been learning a lot lately, as I would like to get to the next level of Business Intelligence.

Let me tell you, there is SO much information out on the web to learn from.

I've been reading about Advanced Analytics in the Microsoft Stack of BI.

First there was the installation of the product.

Then there was downloading and running the sample projects in SSAS.

Then there was PowerPivot and viewing the OLAP Cubes in Excel.

Then there was creating my first KPI and viewing the contents in an SSRS report deployed to the server.

Then there was SharePoint, which I never loaded due to technical difficulties (I haven't given up yet!).

Then there's Performance Point Developer - a snazzy way to produce cool looking Dashboards, Scorecards, KPI all with drill down/up capabilities for the Senior level execs.

The first go-around, I'm trying to digest what the BI stack encapsulates.

Next I'll dive deeper into each of the components until I get a better understanding of how everything integrates together.

The one thing I was real surprised about in this learning exercise was how many smart people there are in Microsoft BI and how willing everyone is to share their knowledge.

I am surprised at how fast I am digesting all the info as I was a little intimidated at first.

I clung to my 15 years of reporting as if that's all there ever will be.

Looking forward to this weeks SQL Saturday in Orlando, Fl.

It's all good!


Installing Sharepoint 2010 after installing Denali doesn't work

I installed SQL-Server Denali on a Windows 7 machine.

After installing Denali, I wanted to load Sharepoint2010.

However, it threw an error when viewing the pre-requisites:

 When attempting the install, I received the following error message:

Will need to research if its possible to load Sharepoint2010 after installing SQL-Server Denali.

This link says it's a know bug...

Tried to download the SharePoint 2010 SP1 from this site --> This did not solve the problem...

This site has promise - can download the patch.