We had an interesting situtation at a client where we could not restore a SQL Server 2008 R2 backup onto SQL Server 2012. The restore would fail at 100% with a deadlock.
A technical blog, from the minds of the Microsoft BI and Custom Dev teams at EOH.
Thursday, August 30, 2012
Logging made simple
This may be old news for most, but for those of you who have not used log4net, this could be quite beneficial…
Monday, August 27, 2012
Isolation Levels
As a follow up to my NOLOCK blog I thought it would be a
good idea to discuss the five different isolation levels in SQL Server. These
are as follows:
Labels:
concurrency,
Dirty Read,
Isolation level,
Non-repeatable,
phantom,
READ UNCOMMITTED,
READCOMMITTED,
READUNCOMMITTED,
REPEATABLE READ,
SERIALIZABLE,
SNAPSHOT,
SQL,
SQL Performance,
SQL Server
Wednesday, August 22, 2012
Blogging Guidelines For Dummies
As I have come to learn in the past few months, the hardest part of a Blog is finding a topic that inspires not only yourself, but will also draw in readers from a variety of backgrounds in the related area of the Blog... For instance, if your area of Blogging is based on a Rugby crowd the biggest mistake you can make is to Blog about The Beautiful Game (Soccer).
Tuesday, August 21, 2012
AGILE
How The FOS team has changed in the past few months- Using agile
I would like to share my experience that I have had on the FOS
team in the past couple of years, and how things changed in the past few months when we
adapted to agile mythology.
In April 2011 was a very stressfull month for our team, we
were all stressed out, under pressure and working long hours. Each member of
the team were busy in their own “world” ; trying to get their tasks completed
in time, which lead to poor quality development and where most of the time work
to be re-done and at time not even tested by our tester before it was release
to the client, because of all the rush
and deadlines. This all happening, making the client frustrated in the process.
Now if I compare what the team is today and what we were
last year April, we have changed as a TEAM – we have grown as a team and
adapted well with Agile.
I believe Agile has
helped us in the following ways:
1.)
Communication
-
Between the team and the client
-
Stand Ups (Being aware of what our team mates
are busy with)
2.)
Weekly Release
-
This is a great opportunity for the client to
see progress and change requirement if necessary in time and not when task is
fully completed where it requires the developer to re-do his/her work.
3.)
More awareness/ Visibility
4.)
Transparency to client and team
5.)
Planning
& Organizing
Monday, August 20, 2012
Laying it out: Onion Architecture
It's a fact, there is no Single Silver Bullet for every solution, but we can come damn close. Having the right architecture sets a solid foundation for any solution. When I say "architecture", I mean structuring the solution in a specific strategic way; with the aim to have the components (or layers) loosely coupled and tightly cohesive to the maximum extent possible keeping in mind the feasibility of the trade-off.
Project Management??
From a young age we all had big dreams of what we want to be when we grown up, some wanted to be firemen, police men, game rangers and some ladies wanted to be models - or the best one: Marry a rich man and spend his money.
Subscribe to:
Posts (Atom)