As you can see from the below slide, these are the identified issues and limitations that we have with the Stretch database within SQL Server 2016 CTP 3.0 release. A table that has more than 1023 columns or 998 indexes is not eligible to stretch it to Azure. Also the constraints like Check, Foreign Key, Default are also a huge restrictions placed on OLTP schema systems. This Stretch database concept highly works with OLAP based systems and /or if any table that is been isolated without any relations to anyother table. You can also check this article to identify whether any tables within your database is qualified for stretch or not.
This article gives a quick glimpse on how to run SQL Server 2016 Upgrade Advisor Preview 1.2 against AdventureWorks2014 OLTP database. Once you shoot the Upgrade Advisor, go to Scenarios and then select the first option “Run the Stretch Database Advisor”. Following this, you will get below screen and then click on Select Databases to Analyze. This will then shoot the blade option to select the databases but requires you to connect to which instance the database is located. In the below example I am connecting to my YSMLab01\SQL2016 instance.
After choosing the instance, I am selecting AdventureWorks2014 database and clicking on Run button.
Following the analyzed database of AdventureWorks2014, it has identified the database size and total number of tables being analyzed. By clicking on this result set it further displays the list of tables with status on eligibility to cloud or not. If it has errors then it gives out the reasons on why it is not selected in blade format.
In here, I am further trying to find the problem on why Person.Person was not selected and one of the reasons is because of Default Value Constraints on one or more columns cannot be part of stretch database.
You can see the same results when the stretch database advisor is run against AdventureWorksDW2008R2 OLAP database here.
Following the success of Data Awareness Programmes conducted in India & Malaysia Stamford college, this new Data Awareness Programme was conducted again in Kuala Lumpur – Malaysia at Maclearn International College on 19/08/2015.
This included a mixed variety of Students from various degrees with in Information Technology. This programme provided the analytical solution based on the data collected within Malaysia. This helped better understand the students to learn and visualize based on their already known information.
This session also included students, teachers & non-teaching staff to enlighten data & bring awareness related to personal, individual, education & social and this was again successfully delivered, by Dr. Subramani Paramasivam and his Malaysian based team members.
The audience were unbelievably surprised with the level of information provided about data and how to learn more about data and analyse and help themselves and their surroundings including friends, family, relations, and local people in and around. The attendees were amazed with the level of information that was provided for about 8 hours with easy to understand slides & related videos.
This programme was specifically targetted to the attendees by providing more information about Microsoft SQL Server Products, Microsoft Releases, Microsoft SQL Server Editions, Database Development, Database Administration and other Microsoft related database & BI related products.
The demos were mainly based on Power Map, Power Pivot, Power BI and the visualization technology on power map really amazed every single attendee in the auditorium.
This was also a good opportunity for DAGEOP UK Ltd to better explain about the Microsoft products, certifications and awards at student level like MTA (Microsoft Technology Associate) & MSP (Microsoft Student Partner).
Students were very much looking forward for further awareness programmes in Malaysia and thrilled.
Data Awareness Programme Delivery by Dr.Subramani Paramasivam
Tan Seri Datuk Seri M Kayveas Speach
When it comes to data modification statements for OLE DB systems, the XACT_ABORT option with ON and OFF functions helps the Developer/Administrator to decide based on the requirements from the business.
For example lets take a stored procedure that will complete fully, only if the UPDATE statements are completed. In this case the XACT_ABORT option should be set to ON like below.
SET XACT_ABORT ON;
By setting this XACT_ABORT option to ON, it does not affect trapping of any errors using TRY-CATCH, but it helps in a scenario where the commit or rollback was successful or not.