Overview, History, Editions, Licensing, And What's New in SQL Server 2008

8/14/2019 Overview, History, Editions, Licensing, And What's New in SQL Server 2008

1/123


2/123

The History of SQL Server

Presented by Scott Whigham


3/123

In 1989, Microsoft (MSFT) was a $200million a year company with no database

product

Ashton-Tate had the popular dBASEpackage

Sybase had DataServer, a new product

It All Began in the 80s


4/123

MSFT signed deal to license SybasesDataServer on OS/2 and other MSFT-

based operating systems

MSFT convinced Ashton-Tate to helpthem market the product

Ashton-Tate/Microsoft SQL Server

Version 1.0 shipping in May, 1989



5/123

Microsoft SQL Server 1.1 shipped in1990

No more Ashton/Tate

Now for Windows 3.0



6/123

Microsoft SQL Server 4.2 releasetimeline

There was no 2.x or 3.x

16-bit originally for OS/2 released in 1992

Windows NT 3.1 32-bit release in 1993

The 1990s


7/123

Original license with Sybase wasrestrictive

MSFT could not add or change features without

Sybases approval Sybase and MSFT parted ways in 1994

The 1990s


8/123

Next up: SQL95 SQL95 was released in Spring, 1995

Technically Microsoft SQL Server 6.0

Replication is here! MSSQL was now one of The Big Guys in the

database world

Sybase, Informix, Oracle, and IBM still strong

The 1990s


9/123

SQL Server 6.5 in 1996 Short release cycle due to pressure from other

companies

Can you say ANSI Standard Compliant? Still built on the old Sybase code

The 1990s


10/123

SQL Server 7.0 in 1998 Total rewrite no more Sybase code!

Language is still Transact-SQL but it starts to fork

Tons of new features Debut of Data Transformation Services

Row-Level locking

OLAP Services debuts

The 1990s


11/123

SQL Server 2000 in 2000 Originally planned as SQL Server 7.5

Not that many new features but far more

powerful Built to work with Windows Server 2000

OLAP Services becomes SQL Server Analysis

Services

Reporting Services debuts a few years later as a

free add-on

The Millenium


12/123

SQL Server 2005 in 2005 Delays caused by integration with .NET team

Made to work with Windows Server 2003

Many new features:

SQL CLR

Integration Services

Full integration of Reporting Services

Database Mirroring

Tighter XML integration

Schemas!

The Millenium


13/123

SQL Server 2008 in 2008 Not a huge step but built for Windows Server

2008

This allows for more memory, better 64-bit support

Some new features but primarily enhancements

Transparent data encryption

Management policies

Geo-spatial data and datatypes Filestream

Backup compression

The Millenium


14/123

SQL Server .NEXT Whats next?

Business Intelligence (BI) continues to grow

Storing images is hot Will we ever see an O.S. built on SQL Server?

The Millennium


15/123

Editions of SQL Server 2008



16/123

Editions

Processors

CompactEdition

ServerEditions

SpecializedEditions

ReferenceTables

What Were Going to Cover


17/123

Microsoft SQL Server 2008 comes intwo flavors:

Server Editions

Enterprise, Standard Specialized Editions

Express, Developer, Workgroup, Web, Compact

Two Main Pain Points


18/123

Microsoft SQL Server 2008 is furthersegmented by processor architecture:

x86

All x64

All except Compact

IA64

Enterprise and Developer only

Processor Architecture


19/123

Server Editions Enterprise (x86, x64, IA64)

Standard (x86, x64)

Specialized Editions

Developer (x86, x64, IA64)

Workgroup (x86, x64)

Web (x86, x64) Express (x86, x64)

Compact (x86)


20/123

SQL Server 2008 Compact Edition Compact is meant to run on phones/portable

devices

Prior names include SQL Server for Windows CE

and SQL Server Mobile Edition

Targets the .NET Framework 3.5

Free! Not discussed further in this videobook

Compact Edition


21/123

Editions

Processors

CompactEdition

ServerEditions

SpecializedEditions

ReferenceTables



22/123

The Server Editions target companiesrunning Windows Server who need:

Large databases

Lots of users Scalability and availability

Enterprise and Standard Editions are also

the most expensive!

Server Editions


23/123

Enterprise Edition is the most powerfuledition available

No hard limit for CPUs or Memory (OS maximum)

This allows for VLDBs (Very Large Databases) Expensive to buy

Used for mission-critical databases and data

warehouses where uptime is paramount (even

across distances)

Enterprise Edition


24/123

Enterprise Edition is: Expensive to buy

Averages around 5x Standard Edition cost

Used for mission-critical databases and data

warehouses where uptime is paramount (even

across distances)

Enterprise Edition


25/123

Standard Edition is the next mostpowerful edition

4 CPU limit but no Memory limit (OS maximum)

This allows for KLDBs (Kinda Large Databases) Okay, so thats not technically an industry term

Used when needs are similar to Enterprise Edition

but budget isnt available

Even with just 4 CPUs you can potentially handle 100sof GBs of data

Standard Edition


26/123

Standard Edition is the next mostpowerful edition

4 CPU limit but no Memory limit (OS maximum)

This allows for KLDBs (Kinda Large Databases) Okay, so thats not technically an industry term

Used when needs are similar to Enterprise Edition

but budget isnt available

Even with just 4 CPUs you can potentially handle 100sof GBs of data

Standard Edition


27/123

Enterprise Edition Standard Edition

Business Critical

Large scale online

transaction processing

(OLTP)

Large scale reporting

Data warehousing

Advanced analytics

Server consolidation

DepartmentalSmall-to-medium scale

OLTP

Reporting and analytics

Comparing the Server Editions


28/123

Enterprise Edition Standard Edition

Number of CPUs O.S. maximum 4

Number of Instances 50 16

Hypervisor support

Database snapshotsParallelism, index, and

DBCC enhancements

Number of clustered nodes 16 2

Database mirroring Full Single-thread

Hot-add CPU, memory

Fast recovery

Comparing the Server Editions


29/123

Editions

Processors

CompactEdition

ServerEditions

SpecializedEditions

ReferenceTables

In the Next Video


30/123

Editions of SQL Server 2008



31/123

Editions

Processors

CompactEdition

ServerEditions

SpecializedEditions

ReferenceTables



32/123

Server Editions Enterprise (x86, x64, IA64)

Standard (x86, x64)


Developer (x86, x64, IA64)

Workgroup (x86, x64)

Web (x86, x64)

Express (x86, x64)

Compact (x86)


33/123

The Specialized Editions are for specificsituations

Developer Edition: for testing and development

Same feature-set as Enterprise Edition but differentlicense, O.S. & hardware requirements/limits

Workgroup: for branches, small depts

Great for replication to remote sites



34/123

Web: ideal for web hosts Licensing allows for low Total Cost of Ownership

(TCO)

Compact: for mobile devices Usually sync up with Enterprise/Standard to

upload/download new data



35/123

Express: free; great for learning orredistributing

Perfect for very small databases with small

numbers of users

The most confusing edition since there are three

versions of Express



36/123

There are three flavors of Express: SQL Server Express

The SQL Server database but without tools, reporting

SQL Server Express with Tools

Same as above but with feature-limited versions of

management and development tools

SQL Server Express with Advanced Services

Same as SQL Server Express with Tools but withreporting, more admin

The Express Editions


37/123

Editions

Processors

CompactEdition

ServerEditions

SpecializedEditions

ReferenceTables



38/123

Enterprise/Developer

Standard Workgroup Web Express

Number of CPUs O.S. maximum 4 2 4 1

Number of

Instances

50 16 16

Memory O.S. maximum O.S. maximum 4GB O.S. maximum 1GB

Database

snapshots

Log shipping

Number of

clustered nodes

16 2

Database

mirroring

Full Single-thread Witness only Witness only Witness only

Replication

Support

Full Full Subscriber only Subscriber only Subscriber only

Data Compression

Transparent Data

Encryption

Comparing the Editions


39/123

Pricing and Licensing SQL Server

2008



40/123

Licensing

Model Virtualization

Cost per

edition



41/123

When you purchase Microsoft SQLServer 2008, you purchase:

A license to run SQL Server on the server

andone of the following: CPU license

Client Access License (CAL) for a user

Client Access License (CAL) for a device

Two Ways to License


42/123

CAL Licensing Model Explained User model: Requires single CAL for each user

who accesses a system running SQL Server.

One user can use the same CAL to access different SQL

Servers separately Source: Database Pricing whitepaper, MSFT 2008

CAL Licensing


43/123

CAL Licensing Model Explained Device model: Requires single CAL for each

device that accesses a system running SQL Server.

Devices can be PC, workstations, terminal, PDA, mobile

phone, etc

CAL Licensing


44/123

User model or Device model? First question: Should you use CPU licensing

instead?

If you cannot/should not use CPU licensing:

Use device model when there are multiple users per

device

Use user model when there are multiple devices per

user

When in doubt, consider user model

CAL Licensing


45/123

Example scenario: Your CRM applicationhas 50 users worldwide but only 10 useat the same time all using their individualworkstations Need a minimum of 10 user CALs

CRM: Customer Relationship Management

CAL Licensing


46/123

CPU Licensing Model Explained Unlimited number of connections, users for a

single CPU

License only needed for physical CPU

A server with one quad-core CPU would require only a

single CPU license

CPU Licensing


47/123

Consider this scenario: DBA installs SQL Server Enterprise Edition on web

server

One web application makes a single connection to

SQL Server

Web application is used by 500 people worldwide

How many licenses do you need?

How MSFT Determines Usage


48/123

Answer: Not enough information toanswer!

Many people think the answer is One CAL since

there is only one app accessing the database

server!

You need to ask a follow-up question

What is the follow-up question you should ask?



49/123

How many of those 500 users will beusing the system at the same time

(concurrently)?

Answer: 10 Then you need 10 user CALs

Answer: 100

Then you need 100 CALs or 1 CPU license


?


50/123

At some point it makes sense to switchfrom CAL to CPU

10 CALs or 1 CPU?

Depends on cost of each Likely to be somewhere between 60 and 90

concurrent users that you save money by using

CPU

Dont forget to add in growth

CPU or CAL?

I h N Vid


51/123

Licensing


Cost per

edition

In the Next Video


52/123

Pricing and Licensing SQL Server

2008


Wh t W G i t C


53/123

Licensing


Cost per

edition


Vi t li ti


54/123

What about licensing when you installSQL Server inside VMware or another

virtualized environment?

Same basic rules For Enterprise Edition, if all processors are

licensed, customers can run unlimited instances

of SQL Server on an unlimited number of virtual

operating environments on that same machine Source: Database Pricing whitepaper, MSFT 2008

Virtualization

Wh t W G i t C


55/123

Licensing


Cost per

edition


Costs (Retail onl )


56/123

Enterprise Standard Workgroup Web

CPU License $24,999 $5,999 $3,899 $15/CPU/month

CAL $8,487 for server

license plus $162 per

CAL

$885 for server license

plus $162 per CAL

$730 for server license

plus $162 per CAL

Not available

Costs (Retail only)

Prices are in U.S. dollars

Source: http://www.microsoft.com/sqlserver/2008/en/us/pricing.aspx, Nov, 2008

Developer Edition: $50 total cost
http://www.microsoft.com/sqlserver/2008/en/us/pricing.aspxhttp://www.microsoft.com/sqlserver/2008/en/us/pricing.aspx


57/123

Whats New in SQL Server 2008


What to Expect


58/123

This is an overview, not a detaileddiscussion

Expect to see Heres what it is and

heres 1 or 2 sentences about it Many if not all will be covered later in

detail

Not all new features are covered

What to Expect



59/123

DBAs Overview of

new featuresand how it

relates toDBAs

Performance

Security

Management

Availability

Deve

lopers T-SQL

Improvements

Datatypes

Geospatial Debugging

Bus

inessIntelligence SSIS

SSRS

SSAS

What We re Going to Cover

SQL 2008 Is About


60/123

SQL 2008 is likely to be interesting tomost people because of its ability to

scale rather than because of new

features While there are lots and lots of new features, only

a few of them are major new features

SQL 2008 Is About

SQL 2008 Is About


61/123

Many of the new features target 5%ers Geospatial support is one such example

Some of the new features are simply

better ways Geospatial support and FILESTREAM are examples

SQL 2008 Is About

SQL 2008 Is About


62/123

If you were creating a first-time app forstoring/working with geospatial data,

SQL Server 2008 would be ideal

What if your app already uses a technique forstoring/working with geospatial data that was

different from the way SQL Server 2008s internal

datatypes and use?

SQL 2008 Is About

SQL 2008 Is About


63/123

A SQL Server 2005 DBA can administer aSQL 2008 box without learning anything

new

Obviously wouldnt be aware of new features andenhancements but it is very possible (and likely)

SQL Server Management Studio (SSMS) has

been augmented but not drastically changed

SQL 2008 Is About

SQL 2008 Is About


64/123

SQL Server 2008 new features furthersegment The Talent

Its not possible for one person to know it all

This was possible as recently as SQL Server 7.0 or even

SQL Server 2000

SQL 2008 Is About

SQL Server 2005 Changed


65/123

In SQL Server 2005, The BusinessIntelligence side of SQL Server matured

thus adding (needed) complexity to

existing products SQL Server

Integration Services (SSIS)

Reporting Services (SSRS) Analysis Services (SSAS)

SQL Server 2005 Changed

Everything

Changing Roles


66/123

Today, its easier to be a Specialist inone area and a Generalist or even a

Deep Generalist in others

You might specialize in SQL Server DBA but havedeep, general knowledge of SSIS, a general

knowledge of SSRS and scant knowledge of SSAS

Changing Roles

SQL Server 2008


67/123

In SQL Server 2008, the DBA must workharder than ever to be a Specialist Fairly easy to be a generalist

Tough to be a deep generalist

Very hard to be a specialist What size databases do you specialize in?

At your last job, did you implement encryption?

Did you do database mirroring and use snapshots at yourlast job?

How many active/active clusters have you built?

Whats the best way to do document/file storage?

SQL Server 2008

Why is this discussion here?


68/123

Why have this discussion now? Dont get intimidated into thinking you have to

know it all

Dont be afraid to say, Thats not my specialty

Pick the areas you like and will need to continue

employment and master those

Why is this discussion here?

In the next video


69/123

DBAs Overview of


relates toDBAs

Performance

Security

Management

Availability

Deve

lopers T-SQL

Improvements

Datatypes


Bus

inessIntell

igence SSIS

SSRS

SSAS

In the next video


70/123



In this video


71/123

DBAs Overview of


relates toDBAs

Performance

Security

Management

Availability

Deve

lopers T-SQL

Improvements

Datatypes


Bus

inessIntell

igence SSIS

SSRS

SSAS

In this video

Performance Improvements


72/123

Compression Enhancements: Backup compression

Are your backups taking up too much space?

Log Stream compression

Are you using database mirroring? If so, log stream

compression can offer significantly better performance

Data compression

Do you have a lot of data that is similar or bloated? Easy to use: BACKUP DATABASE WITH

COMPRESSION




73/123

Enhancements and improvements fordatabases of all sizes

Enhanced/Improved Plan Guide Support

Freezing plan guides, pull plans directly from plan

cache, SSMS integration

p



74/123


Resource Governor

Allows you to manage workload and resources by

setting limits to incoming requests

Can limit certain users/groups/roles to fewer resources

p



75/123


Performance Data Collection

Includes a central repository for storing performance

data as well as tools and reports

p



76/123

Enhancements and improvements forlarger databases:

Partition-aligned indexed views

Are you using indexed views or partitions already? If so,

this is great. If not, probably unnecessary for you at the

moment

Partitioned Table Parallelism

In SQL Server 2005, each partition was limited to asingle thread

p

In this video


77/123

DBAs Overview of


relates toDBAs

Performance

Security

Management

Availability

Deve

lopers T-SQL

Improvements

Datatypes


BusinessIntell

igence SSIS

SSRS

SSAS

Security Improvements


78/123

Lots of new features that are potentiallybetter ways

Transparent Data Encryption

Extends SQL Server 2005 encryption

Easier to turn on/off encryption for the entire database

without having to modify calling applications

y p



79/123

Lots of new features that are potentiallybetter ways

Extensible Key Management (EKM)

Allows the keys that protect the database files to be

stored externally



80/123

Some are just changes New database roles

MSDB database:

db_dts roles have been renamed to be db_ssis

Server group roles: ServerGroupAdministratorRole,ServerGroupReaderRole

Policy-Based Management role:

PolicyAdministratorRole

Data Collector: dc_admin, dc_operator, dc_proxy

In this video


81/123

DBAs Overview of


relates toDBAs

Performance

Security

Management

Availability

Deve

lopers T-SQL

Improvements

Datatypes


BusinessIntell

igence SSIS

SSRS

SSAS

Management Improvements


82/123

New Feature: Policy-Based Management

DBAs can set policies that cover everything from

naming conventions to CLT integration

One of the most exciting new features for DBAs



83/123

New Feature: SQL Server Audit

Allows customizing what you want audited

Allows for auditing at server and database level

SELECT, INSERT, UPDATE, DELETE, EXEC DBCC

Login/logout attempts

State changes

Scripts can be generated from audits



84/123

New Feature: Change Data Capture (CDC)

Allows you to record changes to data into another table

without triggers

INSERT, UPDATE and DELETE

Perfect for applications that update external databases

Example: you need to synchronize two 200GB

databases nightly in a one-hour window



85/123

New Feature: Data Profiling Task

New SSIS Task allows DBAs to profile for things like:

Number of rows

Number of unique values

Percentage of NULL values in column

Duplicate values in potentially key columns



86/123

New Feature:

Extended Events (Xevents)

Capture, filter, and act upon events generated both by

SQL Server, the operating system, and other

applications Can trace events at any level

Can choose aggregated data or event details



87/123

Enhancements

Central Management Servers & Server Groups

DBAs can now designate one SQL Server a Central

Management Server and create a Server Group

Queries can be executed on the servers in the server group

Policies can be evaluated against the group

Changes made in Object Explorer can be propagated

Windows authentication required

In this video


88/123

DBAs Overview of


relates toDBAs

Performance

Security

Management

Availability

Deve

lopers T-SQL

Improvements

Datatypes


BusinessIntelligence SSIS

SSRS

SSAS

Availability Enhancements


89/123

Hot pluggable CPUs

Automatic recovery of suspect pages

Add nodes to peer-to-peer replication

without stopping system activity Enhanced database mirroring

In the next video


90/123

DBAs Overview of


relates toDBAs

Performance

Security

Management

Availability

Deve

lopers T-SQL

Improvements

Datatypes



SSRS

SSAS


91/123



In this video


92/123

DBAs Overview of


relates toDBAs

Performance

Security

Management

Availability

Deve

lopers T-SQL

Improvements

Datatypes



SSRS

SSAS

T-SQL Improvements


93/123

Intellisense is finally here!

Table-valued parameters are here!

Goofy syntax and requirements but you can now

pass table results to stored procedures

Not to user-defined functions though

T-SQL Improvements


94/123

Compound operators are finally here!

SET @i += 1

Declaration and assignment in one

statement is finally here!DECLARE @i INT = 1

T-SQL Improvements


95/123

XML enhancements

Better and easier schema validation

Better XQuery support

Use of let clause to assign values

Full xs:dateTime support

T-SQL Improvements


96/123

FILESTREAM

Allows DBAs and Developers to store documents

as part of the operating system yet to be able to

access those as part of the database

COMMIT/ROLLBACK aware Uses new VARBINARY(MAX) FILESTREAM storage type

Users can use regular SELECT, INSERT, UPDATE, and

DELETE statements to query and modify FILESTREAM

data

In this video


97/123

DBAs Overview of

new featuresand how itrelates toDBAs

Performance

Security

Management

Availability

Deve

lopers T-SQL

Improvements

Datatypes



SSRS

SSAS

Datatypes and Geospatial


98/123

New datatypes for working with

date/time dataDatatype Accuracy Used when

DATETIME 3/1000th of a second Need to store milliseconds

SMALLDATETIME Minute Need to store minutes

DATE Day Need to store only date

TIME 100 nanoseconds Need to store only time

DATETIME2 100 nanoseconds Need more accuracy than 3/1000th

of a second

DATETIMEOFFSET 100 nanoseconds Same as DATETIME2 withTimeZoneOffset capability

New datatypes


99/123

HierarchyId

Used to represent the position in a hierarchy

Has its own functions to work with hierarchical

data

GetAncestor()

IsDescendant()

Geospatial Datatypes


100/123

SQL Server 2008 adds native support for

storing and working with geospatial data

New datatypes:

Datatype Usedwhen More

GEOMETRY Represents a flat 2D surface withX and Y coordinates for points

The GEOMETRY data type doesnt really work as

expected when you pass in latitude and longitude

pairs. For GEOMETRY, the distance between the

POINTS (90 0) and (90 180) is 180 but in GEOGRAPHY,

since both points refer to the same location (the

North Pole), the distance is 0.

GEOGRAPHY Same as GEOMETRY but forEarth

In this video


101/123

DBAs Overview of


Performance

Security

Management

Availability

Deve

lopers T-SQL

Improvements

Datatypes


Bu

sinessIntelligence SSIS

SSRS

SSAS

The Debugger is finally in SSMS


102/123

In SQL Server 2005, the T-SQL Debugger

was not in the SQL Programmers native

environment

SQL Server 2000 included it in the Query Analyzer

SQL Server 2005 forced us to Visual Studio

SQL Server 2008 features the T-SQL

Debugger in SSMS

In the next video


103/123

DBAs Overview of


Performance

Security

Management

Availability

Deve

lopers T-SQL

Improvements

Datatypes


Bu


SSRS

SSAS


104/123



In this video


105/123

DBAs Overview of


Performance

Security

Management

Availability

Developers T-SQL

Improvements

Datatypes


Bu


SSRS

SSAS

SSIS Enhancements


106/123

New SQL Server Integration Services(SSIS) features and enhancementsinclude: C# is finally here!

Scripting is VSTA (Visual Studio Tools forApplications) instead of old SQL Server 2005 way:VSA (Visual Studio for Applications)

Easier to use custom assemblies

Performance improvements such as betterthreading and pipeline scalability

SSIS Enhancements


107/123

More (SSIS) features and enhancements:

Lookups are way better

SQL 2005 had many restrictions and inefficiencies

Limited to ~3GB of memory

OLEDB only Binary matching mean case+accent sensitivity (with

workarounds)

SQL 2008 makes life easier

Persistent Lookups store a cached copy locally

OLEDB, ADO.NET, and flat file sources

More memory

SSIS Enhancements


108/123

New and Improved

Data Profiling Task (already covered)

Change Data Capture makes ETL (Extract,

Transform, Load) easier

New SSIS datatypes for working with new SQL

date/time datatypes

In this video


109/123

DBAs Overview of


Performance

Security

Management

Availability

Developers T-SQL

Improvements

Datatypes


Bu


SSRS

SSAS

Reporting Services

Improvements


110/123

IIS no longer required to be on same

machine to host the Reporting Services

web service

Http.sys now handles HTTP requests just like IIS

Better caching and better memory

management

Improvements

Reporting Services

Improvements


111/123

Tablix data regions for free-form reporting

Reports now can be rendered in MicrosoftWord

Able to respond to 3-4 times the number of

users and their requires on the samehardware compared to SQL Server 2005Reporting Services1

1 Source: Carl Rabeler, Program Manager on the SQL ServerCustomer Advisory Team

Improvements

Reporting Services

Improvements


112/123

Prettier, nicer, better

Microsoft purchased Dundas Data Visualization

technology to use inside SSRS and we now have

Gauges

Better calendar controls Easier to manage charts

Report Builder 2.0

Report Designer

Improvements

In this video


113/123

DBAs Overview of


Performance

Security

Management

Availability

Developers T-SQL

Improvements

Datatypes


Bu

sinessIntel

ligence SSIS

SSRS

SSAS

Analysis Services


114/123

Star JOINs

MERGE statement

Various enhancements


115/123

Deprecated and Discontinued in

SQL Server 2008


What this video covers


116/123

This is an overview, not a complete list

Check Books Online for complete list

Deprecated


117/123

Deprecated items are slated for

removal in a future version, hot fix, or

service release

Discontinued items are things thatdont work that way anymore

Usually Discontinued items were once Deprecated

Discontinued Items that may

affect you


118/123

Some Discontinued items that may affect

you are:

y

Discontinued item Replacement

BACKUP LOG WITH NO_LOG None. Switch to SIMPLE recovery model instead

BACKUP LOG WITHTRUNCATE_ONLY

None. Switch to SIMPLE recovery model instead

60, 65, and 70 compatibility

models

Databases must be at least 80 (SQL Server 2000)

Northwind and Pubs Gone use AdventureWorks instead

Surface Area Configuration

Tool

Lasted only one version SQL Server 2005

Deprecated Items that may

affect you


119/123

Some Deprecated items that may affect

you are:

y

Deprecated item Replacement

BACKUP WITH PASSWORD = None

DATABASEPROPERTY DATABASEPROPERTYEX

sp_dboption ALTER DATABASE

FASTFIRSTROW hint OPTION(FAST n)

sp_dbcmptlevel ALTER DATABASE SET COMPATIBILITY LEVEL

BACKUP TO TAPE Backup to disk onlySET ANSI_NULLS OFF and

ANSI_NULLS OFF

None they will always be one


affect you


120/123

y


SQLOLEDB is not a provider Use SQL Native Client

TIMESTAMP syntax for

ROWVERSION datatype

Use ROWVERSION datatype

text, ntext, and image

datatypes

Use VARCHAR(MAX), NVARCHAR(MAX) and

VARBINARY(MAX)

sp_attach_db CREATE DATABASE FOR ATTACH

sp_change_users_login ALTER USER

DBCC DBREINDEX REBUILD option of ALTER INDEX

DBCC INDEXDEFRAG REORGANIZE option of ALTER INDEX

DBCC SHOWCONTIG sys.dm_db_index_physical_stats


affect you


121/123

y


sp_configure allow updates No effect

sp_configure option priority

boost

No effect

sp_addapprole CREATE APPLICATION ROLE

sp_addlogin CREATE LOGIN

sp_adduser CREATE USER

sp_grantdbaccess CREATE USER

sp_addrole CREATE ROLE

sp_changeobjectowner ALTER SCHEMA or ALTER AUTHORIZATION

sp_defaultdb ALTER LOGIN


affect you


122/123


sp_grantlogin CREATE LOGIN

sp_denylogin ALTER LOGIN DISABLE

sp_revokelogin DROP LOGIN

GRANT ALL

DENY ALL

REVOKE ALL

Must specify permissions independently

Lots of system tables Compatibility views and Catalog views

WRITETEXT

UPDATETEXT

READTEXT

TEXTPTR()

None.


affect you


123/123


3 and 4-part column namesin queries

Use 1 or 2-part names only such as SELECTt.ProductName

GROUP BY ALL Use custom case-by-case solution with UNION, CTE, or

derived table

Documents

Overview, History, Editions, Licensing, And What's New in SQL Server 2008