2008-10-02
3,551 reads
2008-10-02
3,551 reads
Our initial reason for looking at the money data type can be found within the Precision Considerations for Analysis Services Users white paper. In this white paper, we provide extensive examples of the types of precision issues when your SQL relational data source and your Microsoft® SQL Server® Analysis Services cube have different non-matching data types (e.g., if you query one way you get the value 304253.3251, but run the query in another way and you get the value 304253.325100001).
2008-10-02
2,761 reads
2008-05-29
3,933 reads
This is the third articlefrom Dinesh Asanka in the series on the new Data Types in SQL Server 2008. In this article the spatial data types are explored.
2008-02-22
3,730 reads
In this article, we are going to explore the new HierarchyID data type. We are going to show how to implement hierarchies in SQL Server 2005 and than how same thing in can be achived in SQL Server 2008 using the HierarchyID data type.
2008-02-20
4,301 reads
To optimize Transact SQL (T-SQL) data types in SQL Server, learn how each type affects performance -- I/O, RAM and CPU in SQL Server.
2007-12-26
3,745 reads
2007-12-07
4,014 reads
Continuing on with his series on ADTs, Yakov Shlafman takes a look at working with schema changes when your ADT is on a column used as a primary or foreign key.
2007-09-27
2,236 reads
In SQL Server 2005 there is the concept of alias data types, which are similar to user-defined data types in SQL Server 2000. Yakov Shlafman brings us the first part of a series looking at these structures in SQL Server 2000.
2008-05-30 (first published: 2007-06-19)
6,749 reads
The Unique Identifier datatype in SQL Server has tremendous potential to solve many of the issues one finds with Identity fields, other primary keys, etc. However it also has some drawbacks and limitations. Author Sharad Nandwani looks at some of the pros and cons of this datatype.
2004-06-24
14,026 reads
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
By Steve Jones
If you aren’t watching the Ignite keynotes today, then you might have missed the...
Short version You want to get this running as fast as possible. Do these...
I changed my email address in Edit Profile page, but it has no effect...
Comments posted to this topic are about the item The case for "Understanding our...
Comments posted to this topic are about the item Specifying the Collation
I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:
DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'
SELECT p.PersonType,
p.Title,
p.LastName,
c.CustomerID,
c.AccountNumber
FROM Person.Person AS p
INNER JOIN Sales.Customer AS c
ON c.PersonID = p.BusinessEntityID
COLLATE @c
Will this solve my problem? See possible answers