2008-04-22 (first published: 2008-02-22)
3,212 reads
2008-04-22 (first published: 2008-02-22)
3,212 reads
Gaining insight into my SQL Server standard and Windows logins has historically been a challenge in terms of determining password changes, failed login attempts, etc. I have noticed that you have experienced the same issue with your tip entitled 'When was the last time the SQL Server sa password changed' and I have noticed some information in the forums on the topic as well.
2008-04-21
3,407 reads
We have been discussing SQL Server 2005 Express Edition replication-specific features, investigating authentication mechanisms that are available in order to accommodate connection attempts from remote clients interacting with SQL Server-based distributor via Internet Information Services. We will continue coverage of this topic here.
2008-04-21
1,679 reads
This paper summarizes the different ways that developers can integrate SQL Server 2005 Reporting Services capabilities in their applications.
2008-04-18
10,171 reads
Business Intelligence Architect Bill Pearson continues his examination of MDX functions, this time introducing StripCalculatedMembers(). In this article, we expose the function, and then lead a hands-on practice session with examples that reinforce the concepts.
2008-04-18
2,513 reads
A new tool from Red Gate software that helps you generate realistic test data for testing your SQL Server applications.
2008-04-17
3,542 reads
A short review from the perspective of a web hoster on this handy software utility.
2008-04-16
5,463 reads
An interesting script to handle file tasks from within SQL Server.
2008-04-16
5,394 reads
My company is just starting to look at adding functionality to retain historical data for key tables and columns for auditing purposes in many of our SQL Server databases. I have seen some of your recent tips related to triggers (Forcing Trigger Firing Order in SQL Server and Trigger Alternatives in SQL Server - OUTPUT Clause). Based on using triggers or a similar technology, what is the best way to store the historical data?
2008-04-15
5,915 reads
QL 2005 adds two new methods – signing with certificates and impersonation with EXECUTE AS – that can manage cases where the classic method of ownership chaining fails. I explain the two new methods, as well as the old one, and warns you about the pitfalls.
2008-04-15
3,278 reads
By Andy Warren
Somehow two years have elapsed since my last update; hopefully it won’t be that...
By Steve Jones
If someone is trying to convince you it’s not a pyramid scheme, it’s a...
By Steve Jones
I was looking back at my year and decided to see if SQL Prompt...
I have table: t1 in schema1 with 19 billion records. I have another table...
Comments posted to this topic are about the item Minimally Viable Security
Comments posted to this topic are about the item Encoding NULL
What is returned from this code in SQL Server 2025?
SELECT BASE64_ENCODE(NULL)See possible answers