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
Peter runs DeBetta Software , a consulting firm that develops data-driven enterprise solutions. He is also a programming instructor for Wintellect, a training and consulting company, and a frequent speaker on SQL Server and other subjects.
2005-12-23
1,475 reads
This paper describes user instances in SQL Server 2005 Express Edition and how you can use them to simplify adding database functionality to your Visual Studio projects.
2005-12-22
3,002 reads
A few months ago, I posted an article here at DBJ named How to Pass Access Data Across the Web. One reader expressed concern over using the Microsoft Internet Explorer library because of security issues. While I do not share his fear, I appreciate that others might, so I began to think about how the process could be enhanced by substituting a Web Service for the traditional ASP/Querystring web page approach described in the article. What follows is the fruit of those labors.
2005-12-21
2,821 reads
Despite a growing range of options for integrating mixed database environments, some companies are sidestepping the problem by moving to a single database platform.
2005-12-16
2,322 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
With the introduction of SQL Server 2005, Microsoft has created a new .NET management API for SQL Server called SQL Management Objects (SMO). As I started working with SQL Server in earnest following its release I discovered a few limitations that I hoped to correct using SMO. This article describes those problems and how to use SMO to script database objects.
2005-12-14
2,552 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
This article will explore the new Row Versioning feature in SQL 2005, and the two new transaction isolation levels that take advantage of it: Read Committed Snapshot and Snapshot Isolation.
2005-12-12
2,350 reads
After interviewing a number of database geeks, it struck me that many of them focus on one area of database development. Hilary Cotter specializes in replication, for example, while Itzik Ben-Gan focuses on Transact-SQL (see http://www.simple-talk.com/categories/sql-articles). Scott Forsyth is no different, but his area of expertise is more unusual: web hosting using .NET technology.
2005-12-09
2,034 reads
By Steve Jones
With the AI push being everywhere, Redgate is no exception. We’ve been getting requests,...
By Steve Jones
fawtle – n. a weird little flaw built into your partner that somehow only...
AWS recently added support for Post-Quantum Key Exchange for TLS in Application Load Balancer...
Comments posted to this topic are about the item Where Your Value Separates You...
Comments posted to this topic are about the item Fixing the Error
Comments posted to this topic are about the item T-SQL in SQL Server 2025:...
On SQL Server 2025, I have a database that has this collation: SQL_Latin1_General_CP1_CI_AS. I decide I want to run this code:
SELECT UNISTR('*3041*308A*304C*3068 and good night', '*') AS 'A Classic';
I get this error:Msg 9844, Level 16, State 4, Line 24 The char/varchar input type uses an unsupported collation. Only a UTF8 collation is supported with char/varchar input type in UNISTR function.What is the easiest way to fix this error? See possible answers