'SQL Database is a cloud relational database service that helps you focus on rapid app development, accelerating your time to market instead of managing virtual machines and infrastructure. You can combine two design options, elastic database pools and single databases, to create innovative designs. With elastic database pools, as demand changes, the databases in the pool automatically scale up and down for predictable performance, with no downtime and within a predictable budget. If you only have a few databases, you can choose single databases and dial performance up and down, still with no downtime. Either way you go—single or elastic—you’re not locked in, as both benefit from SQL Database’s mission-critical capabilities, performance guarantee and industry-leading 99.99% SLA. See the Introduction to SQL Database to learn more about features and options.'...
https://azure.microsoft.com/en-us/pricing/details/sql-database/
'As I write more code, especially database code, and I collaborate with others (or myself), I find that I have the need to merge code more and more. It’s inevitable, and since I work across a couple machines, I even find that I need to merge my own code at times.
One way to do this well is use a merge tool of some sort. KDiff3 is a popular one, that’s free, and it’s one that integrates nicely with SQL Source Control, which I also use for various tasks.
If you install KDiff3 (use “choco instal kdiff3”) then you get a basic tool that allows you to compare files. If you start it, you’ll get a simple interface that lets you select multiple files and view them together in one interface. If you don’t use version control, apart from making a mistake, you also probably manage code like this.'...
http://www.sqlservercentral.com/blogs/steve_jones/2016/04/18/kdiff3/
'In most companies developers are restricted from accessing the MSDB database and they rarely know the performance of their packages in a production environment unless they have access to third party software tools or a friendly DBA. This happened to me once when I wanted to know how long my packages ran in a production environment and I had no access to the MSDB database to look at the sysjobs and sysschedules tables. The work around is to enable SQL Server logging in SSIS packages and to create a SSRS report from the sysssislog table.'...
https://www.mssqltips.com/sqlservertip/3628/creating-a-ssrs-report-to-show-ssis-package-run-time-statistics/
'Once hampered by limitations, in-memory OLTP will be more robust and complete in SQL Server 2016. Learn about the improvements.'...
http://searchsqlserver.techtarget.com/tip/SQL-Server2016-addresses-in-memory-OLTP-limitations
'Trying to visual a database model is sometimes quite difficult. When the model is small it is pretty easy to have an idea what tables reference other tables. But at the data model gets larger it is often difficult to see exactly how the tables relate. In this tip I show you how you can use the built-in SQL Server database diagram tool. I go through some of them messages you may get when getting started and then look at various tasks that you would perform using this free tool.'...
https://www.mssqltips.com/sqlservertip/1816/getting-started-with-sql-server-database-diagrams/
'LET’S FACE IT, MOST PEOPLE DON’T HAVE JUST ONE SQL SERVER
How many they tell Microsoft they have is another matter, but let the record show that I don’t condone licensing dishonesty. But going one step further, most places… Well, they’re ‘lucky’ if they have one DBA, never mind a team.
Everyone else: Give me your network people, your sysadmin, your huddled SAN group yearning to breathe free, the wretched refuse of your teeming developers.
Doing things on one server is aggravating enough. Doing things on a bunch of servers is even worse. Given some of today’s HA/DR features (I’m looking at you, Availability Groups, with your lack of a mechanism to sync anything outside of user databases. Rude.) people are more and more likely to have lots of SQL Servers that they need to tend to.
Sometimes just keeping track of them is impossible. If you’re one guy with 20 servers, have fun scrolling through the connection list in SSMS trying to remember which one is which. Because people name things well, right? Here’s SQLVM27\Instance1, SQLVM27\Instance2, SQLVM27\Instance3, and that old legacy accounting database is around here somewhere.
REGISTER IT AND FORGET IT'...
https://www.brentozar.com/archive/2016/04/one-weird-trick-for-managing-a-bunch-of-servers/
'We recently released the multi-version support (also known as One Designer) in SSDT 2015, which allows SSIS developers to author, execute, deploy and debug multiple versions of SSIS package from a single version of SSDT designer. With the latest SSDT 2015, SSIS developers can switch the “Target Server Version” property to specify the version of which SSIS package is executed and deployed on. Today, we will show you how to get your custom extensions to be supported by the multi-version support in SSDT 2015.'...
https://blogs.msdn.microsoft.com/ssis/2016/04/19/getting-your-ssis-custom-extensions-to-be-supported-by-the-multi-version-support-of-ssdt-2015-for-sql-server-2016/
'In SQL Server 2014 we introduced a revamped Cardinality Estimator (CE), which we further improved in SQL Server 2016 and Azure SQL Database. With the new CE most workloads are seeing better query plans and thus improved performance.
However, there are some workloads that experience plan regressions and thus performance degradation under new CE. To keep using the old CE you would either use the DB compatibility level 110, or fiddle with trace flags, which you probably don’t want or can do.
In SQL Server 2016 there are a lot of goodies under Compatibility Level 130, such as performance improvements with Columnstore and In-Memory OLTP and all the Query Optimizer enhancements done over the years under Trace Flag 4199. So we are faced with a situation where there are workloads that can benefit from some enhancements that come with Compatibility Level 130, but that cannot use the new CE.'...
https://blogs.msdn.microsoft.com/sqlserverstorageengine/2016/04/27/using-db-compatibility-level-130-with-old-ce-in-sql-server-2016/
'Every time someone tells me, “This database is mission critical – we can’t have data loss or downtime,” I just smile and shake my head. Technology is seriously difficult.
To illustrate, here’s a collection of client stories from the last few years.'...
https://www.brentozar.com/archive/2015/02/9-ways-to-lose-your-data/?utm_source=Brent+Ozar+Unlimited%C2%AE+List&utm_campaign=224ae5a7bb-RSS_EMAIL_CAMPAIGN&utm_medium=email&utm_term=0_8e3e861dd9-224ae5a7bb-296247489
'SQL Server is a database platform designed for providing large-scale transactions, e-commerce applications, data mining, etc. It is widely used on Business platforms for data analysis, data integration and processing components.
Structured Query Language (commonly known as SQL) is a programming language used for managing data held in relational database management system (RDMS) consisting of data definition language, data manipulation language and a data control language. However, the SQL server database consists of three files:
- Primary Database File (MDF file)
- Secondary Database File (NDF file)
- Log file (LDF file)
Among these three, one database file is Log File. The file maintains a log of all the transactions done in SQL Server Database so that information can be later accessed to recover the database. There must exist one log file for each database and it is possible that more than one log file can be created for a single database. The file is in .ldf file extension.
How SQL Server Log File Corrupt?
The log files of the SQL server may be corrupted, i.e. while performing some action upon SQL database, an interruption in between the procedure is probable to occur due to which user first has to repair and recover the log file corrupted SQL server and then continue their transaction.'...
http://www.sqlservercentral.com/blogs/sql-server-citation-sql-blog-by-hemantgiri-s-goswami-sql-mvp/2016/04/26/how-to-recover-data-from-corrupted-log-file-in-sql-server-/