SQL Server Integration Services (SSIS) is an enterprise-level data integration platform. SSIS is an entirely new subsystem in SQL Server 2005. This paper tells you how to take advantage of the SSIS management and deployment features.
How many of you have asked yourself what SQL is all about anyway? Join me as I begin a venture down the road of understanding SQL and how to take advantage of this language.
The following excerpt, courtesy of Addison-Wesley, is from Chapter 6 of the book "A First Look at SQL Server 2005 for Developers" written by Bob Beauchemin, Niels Berglund and Dan Sullivan.
Despite the major advances made with Profiler in SQL Server 2005, auditing changes isn't one of the strengths of the product. New author Sergey Pustovit brings us his technique that allows auditing of actions using shared accounts from an application. A few minor code changes, but overall this is a very interesting idea.
AMO lets developers put their own programs into action. It facilitates client-side custom programming as Decision Support Objects (DSO), the object model in SQL Server 2000 Analysis Services. With AMO, a whole range of data mining questions can be answered at the operational level. This means that sales and marketing departments get answers more quickly and thus can make informed decisions. Specialized resources, like the IT team and analysts, can be brought in when they're needed most.
There are times when a new application or time period requires the creation of a number of logins for your clients. This can be a time consuming process, but Leo Peysakhovich brings us a way to make this go quickly.
Tuning SQL Server for performance is in many ways like constructing a house. You must find a suitable location with rich soil, build a solid foundation to support two or three levels, install the electrical and plumbing, finish the walls for painting and decorating, and finally conduct ongoing maintenance.
When Database Administrators manage multiple databases on multiple servers, it is difficult to keep track of and monitor the used percentage of data portion on every database. Though SQL Server has the capability of auto growth whenever the data portion reaches 100%, it is always advisable to increase the database size manually when it comes to VLDB. This article examines monitoring the percentage used on the data portion of every database and alerting the DBA using threshold settings. This article has been written for SQL Server 2000 server.
One of the best ways to reduce the load on your server and increase application responsiveness is to reduce the number of "round trips" your application makes. This article by Andy Warren shows you a few ways to increase your performance by reducing round trips.
Every organization both maintains and uses reference data sets within its enterprise. And in many of these organizations, there are standards about the definition and use of that reference data, although sometimes those standards are at best silently understood instead of specifically documented. Yet even in the best governed environment, that reference data is bound to eventually be abused, either through value set perturbation or extended usage expectations.
By gbargsley
It's 2 AM. Your phone is going off. Users can't connect to the application,...
By Steve Jones
I discovered a procedure recently that I wasn’t aware of: sp_sequence_get_range. This post looks...
By Arun Sirpal
After a year away getting to grips with AI and its application across the...
Comments posted to this topic are about the item Local Agents
Comments posted to this topic are about the item Detecting Deadlocks
Comments posted to this topic are about the item Introducing the Relational Embedding Retrieval...
By default, how often is the SQL Server Database Engine checking for deadlocks?
See possible answers