Planning for disaster recovery in SQL Server Analysis Services can be tricky. Fortunately SQL Server 2005 introduces the concept of a database synchronization, allowing you to transfer information and meta data from one server to another. Yaniv Mor brings us a look at this feature.
2007-05-02
4,441 reads
Analysis Services and business intelligence are new structures for most of the SQL Server world. BI expert Yaniv Mor brings us another article on Analysis Services, this time explaining the various different options for storing your cube data.
2006-10-31
7,304 reads
For those of you using Analysis Services, Yaniv Mor takes a look at some of the manageablity tools with SQL Server 2005. The way you work with Analysis Services and your cubes has changed dramatically and this is a good overview to get you started.
2006-06-07
6,155 reads
One of the difficult parts of developing anaylsis services cubes is determining which aggregations should be chosen. Yaniv Mor brings us the second part of his series and examines using Usage Based Optimization in SQL Server 2005.
2006-05-30
8,097 reads
Analysis Services 2005 seems like it receives much less notice than most of the other features in the latest version of SQL Server. However it is becoming more widely used in more and more companies. One of the features that can prove useful is the logging of queries. New author Yaniv Mor brings us a look at how this has changed in 2005.
2006-05-16
8,626 reads
It’s been forgotten about and neglected for few years but I’ve decided to dust...
I am honored to announce that I have been renewed as a Microsoft MVP...
By Rohit Garg
🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Comments posted to this topic are about the item Navigating Multi Platform Realities in...
I have tried a number of times to export and then import my SSMS...
For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question: You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?
See possible answers