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 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 Saleem Hakani (Microsoft Corporation) on 1/29/2011 12:19 AM
There are times when you may want to create indexes on large tables which may take huge amount of time (sometimes several hours) and yet you want to make the data available during the creation of Index as your database is being used by thousands of users in the production environment.
HOME   |   Automation   |   Scripts & Tools   |   Article Library   |   Videos   |   Job Board   |   Resources
Copyright 2010 by SQLCOMMUNITY.COM