Friday, May 18, 2012
  
By Saleem Hakani (Microsoft Corporation) on 2/1/2011 9:46 PM
What if you have 100's of SQL Server 2005 in your company and you would like to configure all the servers based on some standards (Example: Surface Area Configuration Properties). Take an example you have just installed a SQL Server and also have configured the surface area configuration (SAC) for that SQL Server based on your standards and now you would like to replicate this configuration to 100's and 1000's of other SQL Servers in your company. How would you do that?
By Bellevue College Student on 2/1/2011 9:09 PM
Post by: Gary Mitchell (Bellevue College, WA)
I chose Stored Procedures as a topic because, while Database Administration can be done without writing them, they are a key to automating many of the administration tasks. The intent is not to determine what can be automated or to cover the T-SQL language, but to cover some features and possible methodologies for stored procedures.
By Bellevue College Student on 2/1/2011 8:42 PM
Author: Nyssa Rogers (Bellevue College, WA)
Some developers use them, and some developers think they're the worst thing since the plague. But what are they?

Here's a basic overview of how to declare cursors and perform basic fetches for procedures that need to look at data one line at a time rather than as a set.

 

By Bellevue College Student on 2/1/2011 8:31 PM
Posted by: Chun-Ming Chen (Bellevue College Student, WA)
Concurrency is an ability that allows multiple users to access the same data at the same time.   However as more users access the data at the same time, the greater the chance for users to change the same set of data at the same time and overwrite each other’s input. The integrity of the data is compromised without the users initiating the operations knowing it. There are four types of concurrency problems:

·       Lost updates
·       Dirty reads (uncommitted dependencies)
·       Nonrepeatable reads (inconsistent analysis)
·       Phantom reads
By Bellevue College Student on 2/1/2011 8:21 PM
Post contributed by: Jun Wong (Bellevue College Student)
Triggers are a part of SQL Server that provides an important set of features that can be utilized for a variety of programming needs. It is essentially a special type of stored procedure that runs when a particular event occurs in the database server.  
HOME   |   Automation   |   Scripts & Tools   |   Article Library   |   Videos   |   Job Board   |   Resources
Copyright 2010 by SQLCOMMUNITY.COM