Professional Documents
Culture Documents
2. TAIL-LOG BACKUP:
In SQL 2012 the database restore GUI is similar to the previous versions but with
several differences.
EXAMPLE:
In this example, for the database TestBR, Restore the database to last backup is taken. This
database is set to full recovery model with Full DB backup taken every hour, differential backup
on every 15 minutes and Tlog backup on every 5 minutes.
In previous versions tail-log backup is taken manually.But here, on the top of that same window
you have a notification message which says that a tail-log backup will be taken of the source
database.
Timeline is also available so that restoration is possible not to the last backup taken
but to a specific point in time in the past.
Read-Only Intent: This improvement is a big step in our connectivity story for Readable
secondaries, which is accepted really well by our customers, both at PASS as well as earlier SDRs.
This improvement gives the customers a way to control the type of workloads that run on their HA
servers and efficiently manage their resources.
SQL Server AlwaysOn AutoStat auto-creates and updates temporary statistics needed for
queries running on the readable secondary. These temporary statistics area stored in TempDB
therefore no physical changes are required in the user database. This allows the optimizer to
generate optimal query plans on secondary replica as it would do on the primary replica and it
does not require any user intervention.
Data Quality Services (DQS) in SQL 2012 leverages an internal Knowledge Base about what
data in specific fields should look like, and once that KB is populated with information about
your data, DQS will be able to ensure high quality data and that your reports will be accurate.
Whats best about the DQS feature is that it doesnt take a highly skilled DBA to configure and
use end users can manage that process themselves.
4. BEEFED UP BI CAPABILITIES:
SQL 2012 includes improved Business Intelligence capabilities, powered by a Project
Crescent. Crescent is part of SQL Reporting Services, and allows users to visually represent
data, enabling an interactive way to gain real business intelligence from the information at hand.
Project Crescent is an interactive data exploration and visual presentation experience targeted at
Information Workers who need access to their business data but dont have the technical knowledge to
write their own queries or specialized knowledge around reporting. Built on top of the BI Semantic
Model, which provides a user friendly view of the data, Project Crescent gives the user a powerful yet
simple to use experience for telling stories with their data.
A further benefit of using AlwaysOn is that mirror servers can be used to create and run reports.
Using Crescent, those reports, or ad-hoc queries, can be run against target servers that are part of
a Database Availability Group, which allows real-time reporting without affecting production
systems
The Sematic Model within Denali enables business intelligence solutions to scale to very large
organizations and includes one mode of use for all types of end users users who create simple
reports, or who are building customer BI applications.
New Visual Studio based IDE comes standalone or integrated (source control, unit testing, etc), is
released with SQL Server Code Name Denali , on the web, and with Visual Studio vNext and is
designed for both database and BI developers
Improved experience for database developers includes declarative, model-based development, integrated
tools with modern language services, ability to work connected and offline with local testing, and offers
SQL Server edition-aware targeting (SQL Server, SQL Azure).
Improved experience for SSIS developers for data flow design, undo/redo, and human readable
packages.
Juneau is comprised of a set of tools to enable developers to build, test, debug, control revisions,
and modify databases and associated applications for various platforms, such as down-level SQL
Server instances, or SQL Azure. Also included are query tools, which may make visits to the
SQL Server Management Studio increasingly rare for developers and DBAs.
7. CLOUD CAPABILITIES:
Even better news, SQL Server 2012 is cloud ready. This means:
Flexible options for deploying SQL 2012 using the same version of SQL that you would
use in a traditional deployment scenario
Quickly deploying SQL and managing it with the same tools that you would use to
manage a traditional implantation
Integration with platforms such as SQL Azure, which will allow organizations to scale
services out rapidly without needing to change platforms.
Following is a list of some of the issues that are solved in the SQL Server 2012
RC0 release:
1. We can now create a user with a password at the database level a contained database
user. The user authentication is done at the database level and the applications just need
to change their connection strings. This solves a very common problem of Orphaned
Users. In case of a failover, users would be able to connect to the secondary server,
without creating logins on the instance hosting the secondary.
2. Collation conflict between the SQL Server instance and the database is one common
problem that every DBA and developer has experienced. In SQL Server 2012, tempdb will
automatically create the temporary objects by using the collation of the Contained
Database, instead of the collation of the server. This works very well if you are working
with one database or multiple databases having the same collation. The issue with queries
joining temporary tables from multiple databases with different collations is still not
resolved.
3. We can get a list of queries and objects that are not contained or cannot be separated
from the instance by using DMVs (sys.dm_db_uncontained_entities (Transact-SQL) and
events (database_uncontained_usage_event). In other words, SQL Server 2012 provides
the information about when the migration crosses the containment boundary.
4. Using the contained databases, a cloud environment can be simulated with clear
boundaries between the database and the SQL Server instance.
CONCLUSION:
SQL server code name Denali is a significant product release that helps
customers continues to build and support mission critical environments. New
tools and enhancements enable breakthrough insight across all levels of the
organization while cloud-ready technologies for application symmetry across
server, private and public cloud helps customers stay agile for the future.