2008-04-22 (first published: 2008-02-22)
3,212 reads
Additional Articles
Identify SQL Server 2005 Standard Login Settings
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
SQL Server 2005 Express Edition - Part 20 - Authenticating Merge Web Synchronization
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
Integrating Reporting Services into Your Application
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
Set Functions: The StripCalculatedMembers() Functio
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
SQL Data Generator
A new tool from Red Gate software that helps you generate realistic test data for testing your SQL Server applications.
2008-04-17
3,546 reads
myLittleAdmin for MS SQL Server 2005
A short review from the perspective of a web hoster on this handy software utility.
2008-04-16
5,463 reads
SQL Server Script to Create Windows Directories
An interesting script to handle file tasks from within SQL Server.
2008-04-16
5,394 reads
Designing Tables for Audit Data in SQL Server
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
Giving Permissions through Stored Procedures
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
Blogs
From Planning to Practice: Setting Up Your FinOps Framework
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
“We love to debate minutiae”
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
Advice I Like: Knots
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Forums
Restoring On Top II
Comments posted to this topic are about the item Restoring On Top II
SQL Art 2: St Patrick’s Day in SSMS (Shamrock + Pint + Pixel Text)
Comments posted to this topic are about the item SQL Art 2: St Patrick’s...
Breaking Down Your Work
Comments posted to this topic are about the item Breaking Down Your Work
Question of the Day
Restoring On Top II
I have a database, DNRTest, that has a number of tables and other objects in it. The other day, I was trying to mock up a test and ran this code on the same server:
-- run yesterday CREATE DATABASE DNRTest2 GO USE DNRTest2 GO CREATE TABLE NewTable (id INT) GOToday, I realize that I need a copy of DNRTest for another mockup, and I run this:
-- run today USE Master BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO RESTORE DATABASE DNRTest2 FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens? See possible answers