Recently, I’ve been asked by a couple of prospective clients how RDX’s service delivery model is the correct choice for their company and their specific environment. It hasn’t been a question that I’ve honestly pondered before until lately; all I really thought about prior to getting asked this question is that we aim to strive to do the best for all of the clients that we work for and with, and that we do a great job at it.
As technology advances and organizations grow, cloud computing and hosting are becoming a part of our organizations more and more. One of the new offerings by Microsoft is their Azure platform with one of the services being the Azure SQL database. While working with the Microsoft Azure platform during a recent project, I discovered the ability to name your own Azure SQL server in the Azure Preview Portal, a feature that isn’t available in the Azure Management Portal. I’d like to share this feature with you.
As business intelligence continues to make a big splash into businesses, SSAS and cubes are becoming a requirement. One of the limitations that DBAs face every day is converting from reading and writing T-SQL statements to being able to read and write MDX with ease. In order help others who may have been thrown into the role, I am going to start a series on MDX code writing. This blog post will be geared towards translating a simple T-SQL SELECT statement into an MDX SELECT statement.
I have found that database snapshots are under-utilized and wanted to show an example of how efficient it is to use them prior to a code deploy for the purpose of recovering a single table or reverting an entire database from a snapshot in the event of unexpected functionality within an application.
If you cannot install SQL Server 2008 because of the known issue in the Setup program, you will have to use the slipstream method to successfully complete an installation of SQL Server. This method involves downloading the service pack package that you want for your architecture and combining that with the original SQL Server 2008 install media.
Recently, I was tasked with building a hierarchy using multiple dimensions. I was advised to use a named query or materialized view to accomplish this because SSAS doesn’t have the capabilities to read the columns/attributes from multiple dimensions. Since I have done this before, I decided to take the AdventureWorks database and give a step-by-step tutorial of how to accomplish this request. Let’s get started!
During your life as a DBA, you will probably have to restore the master database and all the user databases on a new operating system to bring an already existing SQL Server instance online. One of my clients recently had an issue with hardware failure. Our only option was to install SQL Server on a new OS and use the backup files to restore all the databases from the old SQL Server instance. Once the new system was completely built and we restored msdb, we noticed that some of the SQL Server Agent jobs began to fail. Below is the error output from the job history. It states that the CMDEXEC subsystem failed to load.
Have you ever built a dimension in SSAS and received a blue informational warning advising you to:
Recently, I had reports from one of my clients that many of their users were experiencing slowness. While investigating, I found the root cause to be a key lookup on a single function execution, completely unrelated to the activities being performed by the users. A key lookup can be a costly operation that requires additional I/O and ultimately negatively impacts performance. As we all know, the disk subsystem is the slowest part of our environments, so eliminating key lookups when you can and decreasing the amount of I/O will have a positive impact on performance.
Did you ever have one of those déjà vu moments when you are working in SQL Server and you swore you already addressed an issue? This has happened to all of us, and working in SQL Server every day, I’ve certainly had my fair share of SQL déjà vu.