A partitioned table is one where the data is separated into smaller physical structures based on the value for a specific column (called the partitioning column, which is defined in the partition function). If you want to separate data by year, you might use a column called DateSold as the partitioning column, and all data... » read more
Restore a SQL Server 2008 R2 SP3 (10.50.6560) database to SQL Server 2019 (15.0.2000.5). Note: After restore, the database files are same size as original files.
Via Azure Portal, restore a copy of the database from a backup at specific point in time. Via SSMS, copy over deleted records from recovered database back to the original database. Note: In Azure Portal, go to the original database and select “Retore”. Select a point in time before the accidental delete occurred. Time is... » read more
In addition to the automatic failover that occurs for Always On setup, these jobs also needs to be created on both the Primary and the Secondary server to help with the automatic failover. In the event of a failover, all user jobs should be disabled on the Secondary server and enabled on the Primary server... » read more
2 Options to add new Job Category via Script via GUI Via Script Via SSMS In Management Studio, the same process is exposed via a dialog located under the SQL Server Agent Jobs node in the Object Explorer as shown below: Right-click the highlighted item and you are presented with the Manage Job Categories dialog... » read more
Generating Logins Logins are server wide login and password pairs, where the login has the same password across all databases. Here is some sample Transact-SQL that creates a login: You must be connected to the master database on SQL Azure with the administrative login (which you get from the SQL Azure portal) to execute the... » read more
Right click on the Availability Group, select “Failover…” Select the new primary replica Synchronous commit = No data lost Asynchronous commit = Possible data lost Results Validating failover settings for secondary replica Performing manual failover to secondary replica Completing the role change for secondary replica Validating WSFC quorum vote configuration Note: Run the following on... » read more
Manual failover without data loss Use this method when the primary replica is available, but you need to temporarily or permanently change which instance hosts the primary replica. To avoid potential data loss, before you issue the manual failover, ensure that the target secondary replica is up to date. To manually fail over without data... » read more
2 Server Setup Server Role Availability Mode Failover Mode Connections in Primary Role Readable Secondary Seeding Mode Session Timeout Endpoint URL DB01 Primary Synchronous commit Automatic Allow all connections No Manual 180 TCP://<servername>:5022 DB02 Secondary Synchronous commit Automatic Allow all connections No Manual 180 TCP://<servername>:5022 3 Server Setup Server Role Availability Mode Failover Mode Connections... » read more