Windows azure sql database & your data

Editor's Notes

• #5: -
• #9: Master is read-onlyREAD COMMITTED SNAPSHOT does optimistic reads and pessimistic writes. In contrast, SNAPSHOTdoes optimistic reads and optimistic writes.When either the READ_COMMITTED_SNAPSHOT or ALLOW_SNAPSHOT_ISOLATION database options are ON, logical copies (versions) are maintained for all data modifications performed in the database. Every time a row is modified by a specific transaction, the instance of the Database Engine stores a version of the previously committed image of the row in tempdb. Each version is marked with the transaction sequence number of the transaction that made the change. The versions of modified rows are chained using a link list. The newest row value is always stored in the current database and chained to the versioned rows stored in tempdb.READ COMMITTED SNAPSHOT does optimistic reads and pessimistic writes. In contrast, SNAPSHOTdoes optimistic reads and optimistic writes.
• #12: CREATE TABLE [dbo].[TestTable] (    [Id]        UNIQUEIDENTIFIER NOT NULL,    [FirstName] NVARCHAR (10)    NOT NULL,    [LastName]  NVARCHAR (10)    NOT NULL,    [Type]      INT              NOT NULL,    [Timestamp] ROWVERSION       NOT NULL,    PRIMARY KEY (Id));
• #13: CREATE TABLE [dbo].[TestTable] (    [Id]        UNIQUEIDENTIFIER NOT NULL,    [FirstName] NVARCHAR (10)    NOT NULL,    [LastName]  NVARCHAR (10)    NOT NULL,    [Type]      INT              NOT NULL,    [Timestamp] ROWVERSION       NOT NULL,    PRIMARY KEY NONCLUSTERED (Id));CREATE CLUSTERED INDEX IX_TestTable on TestTable (FirstName, LastName);
• #14: CREATE CLUSTERED INDEX IX_TestTableON TestTable ([Type],[FirstName],[LastName])WITH (DROP_EXISTING=ON)ON [Primary]
• #15: CREATE CLUSTERED INDEX IX_TestTableON TestTable ([Type],[FirstName],[LastName])WITH (DROP_EXISTING=ON)ON [Primary]
• #16: CREATE CLUSTERED INDEX IX_TestTableON TestTable ([Type],[FirstName],[LastName])WITH (DROP_EXISTING=ON)ON [Primary]
• #17: CREATE INDEX [IX_TestTable_Country_City_LastName_FirstName]     ON [dbo].[TestTable]     ([Country] ASC,[City] ASC,[LastName] ASC,[FirstName] ASC)    WITH(ONLINE=ON);
• #18: CREATE INDEX [IX_TestTable_Country_City_LastName_FirstName]     ON [dbo].[TestTable]     ([Country] ASC,[City] ASC,[LastName] ASC,[FirstName] ASC)    WITH(ONLINE=ON);
• #19: CREATE INDEX [IX_TestTable_Country_City_LastName_FirstName]     ON [dbo].[TestTable]     ([Country] ASC,[City] ASC,[LastName] ASC,[FirstName] ASC)    WITH(ONLINE=ON);
• #20: CREATE INDEX [IX_TestTable_Country_City_LastName_FirstName]     ON [dbo].[TestTable]     ([Country] ASC,[City] ASC,[LastName] ASC,[FirstName] ASC)    WITH(ONLINE=ON);
• #21: CREATE INDEX [IX_TestTable_Country_City_LastName_FirstName]     ON [dbo].[TestTable]     ([Country] ASC,[City] ASC,[LastName] ASC,[FirstName] ASC)    WITH(ONLINE=ON);
• #22: Go to portalCreate Clustered Indexes on the tables’ Natural Keys. Natural Keys, are the fields that best identify the row’s data. For example, the Primary Key used for a table might be a Unique Identifier or a Big Int, but I might access data through a combination of columns. For a car these columns could be Year, Make, Model and VIN. When you create the Clustered Index, order the columns by their selectivity and use this same order when you query for the information.Create Non-Clustered Indexes on your Primary KeysCreate Non-Clustered Indexes for all Foreign KeysCreate Non-Clustered Indexes for columns that are used in WHERE, ORDER BY, MERGE, JOIN and other clauses that require matching data.
• #25: Go to the portal
• #27: Maximum 150 GB
• #28: Geo Redundant Secondary Read Only Access
• #29: Sizes are set and the database des not automatically grow
• #36: dbForge Studio for SQL Server
• #38: CREATE DATABASE [NewDatabaseName] AS COPY OF ServerName.[SourceDatabase]SELECT * FROM sys.dm_database_copies
• #39: Transactions that take too long get killed or if the log goes over 2gb
• #40: Transactions that take too long get killed or if the log goes over 2gb
• #41: Transactions that take too long get killed or if the log goes over 2gb
• #44: Transactions that take too long get killed or if the log goes over 1gb