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,649 reads
In this lesson, we revisit usage-based optimization, a subject that we undertook in my article MSAS Administration and Optimization: Simple Cube Usage Analysis, in September of 2003, and MSAS Administration and Optimization: Toward More Sophisticated Analysis in October of 2003. In the earlier articles, we discovered that, among several tools that Microsoft SQL Server 2000 Analysis Services offered us to assist in the maintenance and optimization of our cubes, two of these tools, the Usage Analysis Wizard and the Usage-Based Optimization Wizard, leveraged the usage-based optimization features of Analysis Services.
2006-01-10
1,810 reads
It has been widely publicized that Analysis Services 2005 uses XML for Analysis 1.1 (XMLA) as its only network protocol for communication between client and server. XMLA is standard public protocol defined by XMLA council and full description can be found at www.xmla.org
2005-12-26
1,771 reads
In this lesson, we revisit Named Sets, a subject that we undertook in my article MDX in Analysis Services: Named Sets in MDX: An Introduction, in March of 2004. There, we introduced Named Sets from the perspective of the MDX query language, having obtained brief exposure to the concept of Named Sets earlier in the MDX in Analysis Services series (Using Sets in MDX Queries). We examined Named Sets as they existed within Analysis Services 2000, touching upon them from the perspective of Analysis Manager, the Cube Editor, and related interfaces in Analysis Services.
2005-12-15
2,193 reads
One of the many tasks of the SQL Server Database administrator is to take and maintain backups of SQL Server databases. This includes taking backups of analytical databases as well. Read on to learn how to backup an Analysis service database.
2005-12-13
2,193 reads
In this article, we will begin an extended examination of the MDX surrounding drilling up and down within our Analysis Services cubes. Comprising an analytical technique by which an information consumer can maneuver between summarized ("drilling up") and detailed ("drilling down") levels of data, drilling up or down occurs along the lines of drilling paths that are defined within the physical structures of our cubes. Often specified by the cube's dimensional hierarchies, these paths can also be based upon alternative relationships that exist within or between dimensions.
2005-11-11
2,036 reads
In this article, I will introduce a significant improvement that underlies the new Analysis Services development approach, the Data Source View. A Data Source View is a design-time object that makes its home in the workbench environment of the Business Intelligence Development Studio.
2005-10-20
2,655 reads
Throughout this and other of my series, we have examined parameterization and parameter picklist support. While my focus has often been support of picklists using datasets generated through MDX queries against the cube under consideration, I have often found myself in client engagement scenarios where differing reporting requirements, as well as various "exceptions," drive a need to extend picklist support beyond the capabilities of the basic MDX queries that we have examined.
2005-10-05
2,506 reads
n this lesson, we will examine another function / property in the MDX toolset, the .UniqueName function. The general purpose of the .UniqueName function is to return the Unique Name of the object to which it is appended. .UniqueName can be used in conjunction with hierarchies, dimensions, levels, and members, in a manner similar to the .Name function that we examined in String Functions: The .Name Function, and, also like .Name, .UniqueName can be useful in a host of different applications.
2005-09-19
1,744 reads
Discover the new Analysis Services 2005 drillthrough architecture. See how to set up drillthrough in Analysis Services 2005 and get guidance on migrating drillthrough settings from Analysis Services 2000 databases.
2005-08-16
1,966 reads
Every organization I talk to has the same problem dressed up in different clothes....
By DataOnWheels
I am delighted to host this month’s T-SQL Tuesday invitation. If you are new...
By alevyinroc
Ten years (and a couple jobs) ago, I wrote about naming default constraints to...
Comments posted to this topic are about the item The day-to-day pressures of a...
Comments posted to this topic are about the item Using OPENJSON
Comments posted to this topic are about the item Data Modeling with dbt for...
I have some data in a table that looks like this:
BeerID BeerName brewer beerdescription 1 Becks Interbrew Beck's is a German-style pilsner beer 2 Fat Tire New Belgium Toasty malt, gentle sweetness, flash of fresh hop bitterness. 3 Mac n Jacks Mac & Jack's Brewery This beer erupts with a floral, hoppy taste 4 Alaskan Amber Alaskan Brewing Alaskan Brewing Amber Ale is an "alt" style beer 8 Kirin Kirin Brewing Kirin Ichiban is a Lager-type beerIf I run this, what is returned?
select t1.key
from openjson((select t.* FROM Beer AS t for json path)) t1 See possible answers