2006-12-25
2,934 reads
Additional Articles
SSIS: Using stored procedures inside an OLE DB Source component
This short blog post looks at how you can use a stored procedure as a data source.
2006-12-22
2,284 reads
Techniques for Uniquely Identifying Database Records
When designing and creating a data model for a data-driven application, the records in tables must each be uniquely identifiable. By having a unique value associated with each record, individual records can be selected, updated, or deleted. Being able to uniquely identify records is so important and standard in a database system that databases allow those designing a database table to specify what column (or columns) make up the primary key.
2006-12-22
3,518 reads
Tales of Corporate Espionage
All good detective stories have a femme fatale. In the case of corporate espionage scandals, Celia Goodson, a seasoned businesswoman and once a glossily groomed blonde, has been involved in investigating more business transgressions to hit the City in the last three decades than anyone else of her years.
2006-12-21
2,627 reads
SQL Server 2005 Service Broker Plays Well with Older Relatives
You can leverage SQL Server 2005 Service Broker with existing technologies such as SQL Server 2000 and MSMQ. BizTalk and SSB external activation are viable options, but a simple polling solution is easier.
2006-12-20
2,465 reads
Your Field Guide To Designing Security Into Networking Protocols
We'll go over some examples of attacks against protocols and rules following, which will help you when designing and implementing protocols of your own.
2006-12-19
1,808 reads
2006-12-18
1,665 reads
CLR Inside Out
This article is meant to explore these architectural issues from the bottom up, and aims to guide you through this new world. In the long run, new programming models are likely to appear that will abstract away a lot of the challenges you will encounter.
2006-12-15
2,929 reads
New SQL Truncation Attacks And How To Avoid Them
In this article I will discuss some new ideas that can result in either modifying SQL statements or injecting SQL code even if the code has escaped the delimiting characters. I will start with some best practices for constructing delimited identifiers and SQL literals, and then I'll show you new ways attackers can inject SQL code in order to help you protect your applications.
2006-12-14
4,373 reads
Getting Started with SQL Server Integration Services
Check out SSIS, the SQL Server 2005 replacement for the older Data Transformation Services. You might find SSIS to be a great solution for automating SQL Server.
2006-12-13
2,992 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