SQL Server 2012 Training

The name for the next release of SQL Server was announced yesterday at the SQL PASS conference as SQL Server 2012. Previously the next release of SQL Server had the codename “Denali”.

WARDY IT Solutions has been developing training for SQL Server 2012 over the past few months and we are proud today to announce the first SQL Server 2012 training in Australia.

Today marks the release of our SQL Server 2012 First look course. This one-day instructor-led training course provides participants a hands-on opportunity to see how SQL Server 2012 will assist organizations to manage mission-critical workloads and provide rich reporting and analytical solutions. The course is running in Sydney and Brisbane on the following dates for the special price of only $199.00 ex. GST:

Sydney – 17th November

Brisbane – 18th November

You can register for the SQL Server 2012 First look course here.

WARDY IT Solutions is also currently developing the following training courses for SQL Server 2012 that will be available soon:

  • Reporting with Power View (Project Crescent)
  • Data Quality and Master Data Services

Getting Value from SQL Server Monitoring

The core role of a Database Administrator is protecting the data assets of an organisation. However today’s DBA is juggling many different roles and responsibilities; from day-to-day operational support through to project delivery. As a result of these conflicting priorities, essential database monitoring is often overlooked. WARDY IT Solutions has recently recorded a presentation that shows how you can get more value from SQL Server Monitoring. In this presentation you will see how the performance monitoring features in Microsoft SQL Server 2008 R2 can assist to ensure the availability and reliability of your SQL Server topology.

Getting Value from SQL Server Monitoring – Part 1

Getting Value from SQL Server Monitoring – Part 2

Getting Value from SQL Server Monitoring – Part 3

Getting Value from SQL Server Monitoring – Part 4

Getting Value from SQL Server Monitoring – Part 5