Limitations in SQL Azure |
The fundamental differences between SQL Server and SQL Azure lie in the basic design principals of cloud computing, in which performance, ease of use, and scalability must be carefully balanced |
|
|
SQL Server 2008 : Performance Data Collection (part 1) |
Performance data collection is one of the most significant new features for SQL Server Administrators. Performance data collection builds on the strengths of the DMVs to provide long-term data storage and reporting based on this data. |
|
SQL Server 2008 : Performance Tuning - Partitioning |
Organizations collect more data and retain data for longer than ever before. The phenomenal growth of the storage manufacturing industry over the past 10 years is a testament to continually increasing data collection |
|
SQL Server 2008 : Guide to the DYNAMIC Management Views (DMVs) |
DMVs are almost certainly the single most useful tool for troubleshooting and performance tuning for SQL Server databases. DMVs and DYNAMIC Management Functions (DMFs) provide Administrators with a simple yet powerful insight into the workings of SQL Server and hardware resources (disk, memory, CPU). |
|
|
SQL Server 2008 : Managing Security - Security and SQL Agent |
SQL Server job steps often need to do more than just execute Transact-SQL. In order to perform tasks such as operating system commands (CmdExec), executing Integration Services packages, and PowerShell scripts, various credentials often associated with Windows logins are necessary |
|
|
|
|
|
SQL Azure Primer (part 2) - Configuring the Firewall |
SQL Azure implements a firewall on your behalf. That's a benefit that helps protect your database. Indeed, the default firewall rule is that no one can connect. Allowing no connections by default is a good security practice |
|
SQL Azure Primer (part 1) |
As you've seen, SQL Azure is a relational database engine based on SQL Server technology. It supports many of the features of SQL Server including tables, primary keys, stored procedures, views, and much mor |
|
|
SQL Server 2008 : Isolation Level Explained |
Isolation levels are how SQL Server decides what level of locking to take when working with data. There are five isolation levels available for your transactions in SQL Server 2008: READ UNCOMMITED, READ COMMITED, REPEATABLE READ, SNAPSHOT, and SERIALIZABLE |
|
SQL Server 2008 : ACID |
ACID (Atomicity, Consistency, Isolation, and Durability) is the basic foundation upon which transactions are built. In order to be considered a transaction, the statement must fulfill these foundations. |
|
SQL Server 2008 : Transactions Explained |
Transactions are logical groups of commands that are committed to the database or rolled back in the database at the same time. This allows you to insert, update, and delete several different tables and revert those changes if a single command within the transaction fails, or commit all the work if there are no errors. |
|
SQL server 2008 : Handling Errors (part 3) |
SQL Server 2005 and 2008 provide you with a powerful error handling feature in your T-SQL code: a TRY and CATCH control of flow statement. This error handling technique is similar to exception handling, which exists in programmability languages |
|
SQL server 2008 : Handling Errors (part 2) |
The @@ERROR function returns the error ID number generated by the most recent statement executed by a user. If the value returned is zero, then no error occurred. This function is available in all versions of SQL Server, and it’s the only way to handle errors in version 2000 and previous of SQL Server. |
|
SQL server 2008 : Handling Errors (part 1) |
The @@ERROR function returns the error ID number generated by the most recent statement executed by a user. If the value returned is zero, then no error occurred. This function is available in all versions of SQL Server, and it’s the only way to handle errors in version 2000 and previous of SQL Server. |
|
|
|
|
|
|
SQL Server Integration Services : Logged and Nonlogged Operations |
Bulk-copy operations can occur in two modes: logged and nonlogged (also known as slow and fast bcp, respectively). The ideal situation is to operate in nonlogged mode because this arrangement dramatically decreases the load time and consumption of other system resources, such as memory, processor use, and disk access |
|
SQL Server Integration Services : Using bcp (part 5) |
If you are not making use of fixed-width fields or length prefixes, you must use a field terminator to indicate the character(s) that separates fields; for the last field in the data row, you must also indicate which character(s) ends the line. |
|
|
|
|