SQL Server 2005 Integration Services - Part 39 - Send Mail Task
Among the most common tasks that have not yet been discussed in this series is the Send Mail task, which will be the topic of this article.
2007-01-08
2,394 reads
Articles
A Lap Around SQL Server 2005 Compact Edition
With a new name, new capabilities, and a new focus, the product formerly called SQL Server Mobile Edition expands its reach to small-footprint desktop applicationsand it's free!
2007-01-04
2,923 reads
Eliminating Tape
In response to an editorial on eliminating tape in favor of disk backups, new author Tim OPry brings us a look at his environment and the process by which they eliminated the need for tape in their backup scheme while maintaining a well thought out disaster plan.
2007-01-03
7,162 reads
Using Synonyms in SQL Server 2005
It's nice to have little amenities in your development tools. They make for easier development and can save you a little time. Synonyms is one of those tools.
2007-01-03
3,795 reads
Populating Fact Tables
Part 3 of Vincent Rainardi's data warehousing series looks at some of the situations and challenges of loading a fact table in a data warehouse.
2007-01-02
45,601 reads
Product Discussions, Questions, and Comments
In response to a number of suggestions, we have setup new forums where you can ask and comment about the various third party products that you use with SQL Server.
2007-01-02
1,364 reads
Security Enhancements in SQL Server 2005: Schema
Security has become more and more important in today's business environment. From the database point of view, DBAs and system administrators need an improved security model. SQL Server 2005 provides an improved security feature. It is claimed that SQL Server 2005 is secure by default. In SQL Server 2005, the security model is divided into three areas namely authentication, authorization, and encryption.
2006-12-29
2,741 reads
Processing event logs using DumpEvt and SQL Server
As a DBA, you can find very useful information in the Windows event logs. About important events, the health of your SQL Server and the operating system it runs on. Unfortunately, the logs also contain a lot of useless information. Some applications have a tendency to log hundreds of events every day, filling up the logs very quickly with info that you, as a DBA, do not need. But you still need to see that important message that informs you the server is going to crash if you don’t take action.
2006-12-28
2,298 reads
Using SQL Server to Implement the Publish-Subscribe Integration Patter
Utilizing design patterns with SQL Server 2005 Service Broker enables you to assess and select appropriate solutions for all of your SQL Server 2005 asynchronous messaging needs.
2006-12-27
2,224 reads
SQL Server Spotlight on Richard Waymire
Contiuing with our popular series of interviews with the SQL Server developer team, Steve Jones takes a few minutes with Richard Waymire, longtime team member.
2006-12-26
2,139 reads
Blogs
Trace Flag 1448 – Lessons from a Technical Interview
By gbargsley
In SQL Server environments where transactional replication runs alongside Always On Availability Groups (AGs),...
Disable the sa login in SQL Server (and sleep better)
Disable the sa login in SQL Server (and sleep better)If you run SQL Server...
Leadership in Times of Change: Guiding Teams Through Uncertainty, Disruption, and Transformation
By Chris Yates
Change is inevitable. What separates thriving organizations from those that falter is not the...
Forums
Create an HTML Report on the Status of SQL Server Agent Jobs
Comments posted to this topic are about the item Create an HTML Report on...
Be Wary of Data
Comments posted to this topic are about the item Be Wary of Data
Locking Hierarchies
Comments posted to this topic are about the item Locking Hierarchies
Question of the Day
Locking Hierarchies
You have a table [dbo].[orders] without a Clustered Index (Heap). The table does not have any other nonclustered indexes! You rund the following command in Read Committed Isolation Level:
SELECTo_orderdate,
o_orderkey,
o_custkey,
o_storekey
FROMdbo.orders
WHEREo_orderkey = 3877;