Why Sitecore 9 xDB on SQL server 2016?

Clash Royale CLAN TAG#URR8PPP

up vote
4
down vote

favorite

My curiosity is to know more about the features which Microsoft has provided in the SQL server 2016 version which also allows the Sitecore to implement the xDB on the SQL Server 2016 itself, which was not possible before.

I totally agree, of having the advantage of Microsoft only infrastructure in the Sitecore solution, so we don’t have to maintain the 2 database administrators and infrastructure.

It would be great if someone can explain what’s was the problem/bottleneck of the older version of SQL server(prior to 2016 ), which could not handle the xDB requirement and what exactly they introduce in SQL server 2016, which makes it possible for Sitecore xDB to handle the high performance when data is growing at fast rate.

Any documentations on the gaps which Microsoft SQL server has had before, which they filled in the version 2016 from Sitecore xDB points of view?

xdb sql-database

share|improve this question

asked Aug 31 at 9:43

Ashish Bansal

925213

add a comment | 

up vote
4
down vote

favorite

My curiosity is to know more about the features which Microsoft has provided in the SQL server 2016 version which also allows the Sitecore to implement the xDB on the SQL Server 2016 itself, which was not possible before.

I totally agree, of having the advantage of Microsoft only infrastructure in the Sitecore solution, so we don’t have to maintain the 2 database administrators and infrastructure.

It would be great if someone can explain what’s was the problem/bottleneck of the older version of SQL server(prior to 2016 ), which could not handle the xDB requirement and what exactly they introduce in SQL server 2016, which makes it possible for Sitecore xDB to handle the high performance when data is growing at fast rate.

Any documentations on the gaps which Microsoft SQL server has had before, which they filled in the version 2016 from Sitecore xDB points of view?

xdb sql-database

share|improve this question

asked Aug 31 at 9:43

Ashish Bansal

925213

add a comment | 

up vote
4
down vote

favorite

up vote
4
down vote

favorite

My curiosity is to know more about the features which Microsoft has provided in the SQL server 2016 version which also allows the Sitecore to implement the xDB on the SQL Server 2016 itself, which was not possible before.

I totally agree, of having the advantage of Microsoft only infrastructure in the Sitecore solution, so we don’t have to maintain the 2 database administrators and infrastructure.

It would be great if someone can explain what’s was the problem/bottleneck of the older version of SQL server(prior to 2016 ), which could not handle the xDB requirement and what exactly they introduce in SQL server 2016, which makes it possible for Sitecore xDB to handle the high performance when data is growing at fast rate.

Any documentations on the gaps which Microsoft SQL server has had before, which they filled in the version 2016 from Sitecore xDB points of view?

xdb sql-database

share|improve this question

asked Aug 31 at 9:43

Ashish Bansal

925213

My curiosity is to know more about the features which Microsoft has provided in the SQL server 2016 version which also allows the Sitecore to implement the xDB on the SQL Server 2016 itself, which was not possible before.

I totally agree, of having the advantage of Microsoft only infrastructure in the Sitecore solution, so we don’t have to maintain the 2 database administrators and infrastructure.

It would be great if someone can explain what’s was the problem/bottleneck of the older version of SQL server(prior to 2016 ), which could not handle the xDB requirement and what exactly they introduce in SQL server 2016, which makes it possible for Sitecore xDB to handle the high performance when data is growing at fast rate.

Any documentations on the gaps which Microsoft SQL server has had before, which they filled in the version 2016 from Sitecore xDB points of view?

xdb sql-database

share|improve this question

asked Aug 31 at 9:43

Ashish Bansal

925213

share|improve this question

share|improve this question

asked Aug 31 at 9:43

Ashish Bansal

925213

asked Aug 31 at 9:43

Ashish Bansal

925213

asked Aug 31 at 9:43

Ashish Bansal

925213

925213

add a comment | 

add a comment | 

2 Answers
2

active

oldest

votes

up vote
1
down vote

I think that JSON data type and specific JSON related functions that were introduced in MS SQL Server 2016 are major reason why xConnect and xDB starting from Sitecore 9 can finally support also "xDB requirements".

Also introduction of xConnect as an API for xDB helped achieved this as it abstracted previous close tight of xDB with Mongo DB and made underlying DB "irrelevant".

share|improve this answer

answered Aug 31 at 10:00

Peter Prochazka

3,2141530

add a comment | 

up vote
1
down vote

One of the most important SQL Server 2016 features required by xDB is always encrypted which provides data at rest encryption. It's supported by MongoDB in Sitecore 8 xDB while SQL Server 2016 provides the same feature for Sitecore 9 xDB.

As a side note, SQL Server 2016 also added support for JSON, but xDB does not really use JSON data type in SQL.

share|improve this answer

edited Aug 31 at 11:05

answered Aug 31 at 10:03

grg

1,119111

• 
  
  
  

  
  

  
  
  
  
  
  

  
  I think, Mongo DB also support the GDPR compliance, as most of the application still running on MongoDB with Sitecore
  – Ashish Bansal
  Aug 31 at 10:15
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @AshishBansal, yes, GDPR compliance can be achieved with both Mongo and SQL Server. I removed the note about GDPR as data at rest encryption is not strictly a requirement.
  – grg
  Aug 31 at 11:01
  
  

  
  
  
  

add a comment | 

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "664"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f13635%2fwhy-sitecore-9-xdb-on-sql-server-2016%23new-answer', 'question_page');

);

Post as a guest

Name Email

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

active

oldest

votes

active

oldest

votes

up vote
1
down vote

I think that JSON data type and specific JSON related functions that were introduced in MS SQL Server 2016 are major reason why xConnect and xDB starting from Sitecore 9 can finally support also "xDB requirements".

Also introduction of xConnect as an API for xDB helped achieved this as it abstracted previous close tight of xDB with Mongo DB and made underlying DB "irrelevant".

share|improve this answer

answered Aug 31 at 10:00

Peter Prochazka

3,2141530

add a comment | 

up vote
1
down vote

I think that JSON data type and specific JSON related functions that were introduced in MS SQL Server 2016 are major reason why xConnect and xDB starting from Sitecore 9 can finally support also "xDB requirements".

Also introduction of xConnect as an API for xDB helped achieved this as it abstracted previous close tight of xDB with Mongo DB and made underlying DB "irrelevant".

share|improve this answer

answered Aug 31 at 10:00

Peter Prochazka

3,2141530

add a comment | 

up vote
1
down vote

up vote
1
down vote

I think that JSON data type and specific JSON related functions that were introduced in MS SQL Server 2016 are major reason why xConnect and xDB starting from Sitecore 9 can finally support also "xDB requirements".

Also introduction of xConnect as an API for xDB helped achieved this as it abstracted previous close tight of xDB with Mongo DB and made underlying DB "irrelevant".

share|improve this answer

answered Aug 31 at 10:00

Peter Prochazka

3,2141530

I think that JSON data type and specific JSON related functions that were introduced in MS SQL Server 2016 are major reason why xConnect and xDB starting from Sitecore 9 can finally support also "xDB requirements".

Also introduction of xConnect as an API for xDB helped achieved this as it abstracted previous close tight of xDB with Mongo DB and made underlying DB "irrelevant".

share|improve this answer

answered Aug 31 at 10:00

Peter Prochazka

3,2141530

share|improve this answer

share|improve this answer

answered Aug 31 at 10:00

Peter Prochazka

3,2141530

answered Aug 31 at 10:00

Peter Prochazka

3,2141530

answered Aug 31 at 10:00

Peter Prochazka

3,2141530

3,2141530

add a comment | 

add a comment | 

up vote
1
down vote

One of the most important SQL Server 2016 features required by xDB is always encrypted which provides data at rest encryption. It's supported by MongoDB in Sitecore 8 xDB while SQL Server 2016 provides the same feature for Sitecore 9 xDB.

As a side note, SQL Server 2016 also added support for JSON, but xDB does not really use JSON data type in SQL.

share|improve this answer

edited Aug 31 at 11:05

answered Aug 31 at 10:03

grg

1,119111

• 
  
  
  

  
  

  
  
  
  
  
  

  
  I think, Mongo DB also support the GDPR compliance, as most of the application still running on MongoDB with Sitecore
  – Ashish Bansal
  Aug 31 at 10:15
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @AshishBansal, yes, GDPR compliance can be achieved with both Mongo and SQL Server. I removed the note about GDPR as data at rest encryption is not strictly a requirement.
  – grg
  Aug 31 at 11:01
  
  

  
  
  
  

add a comment | 

up vote
1
down vote

One of the most important SQL Server 2016 features required by xDB is always encrypted which provides data at rest encryption. It's supported by MongoDB in Sitecore 8 xDB while SQL Server 2016 provides the same feature for Sitecore 9 xDB.

As a side note, SQL Server 2016 also added support for JSON, but xDB does not really use JSON data type in SQL.

share|improve this answer

edited Aug 31 at 11:05

answered Aug 31 at 10:03

grg

1,119111

• 
  
  
  

  
  

  
  
  
  
  
  

  
  I think, Mongo DB also support the GDPR compliance, as most of the application still running on MongoDB with Sitecore
  – Ashish Bansal
  Aug 31 at 10:15
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @AshishBansal, yes, GDPR compliance can be achieved with both Mongo and SQL Server. I removed the note about GDPR as data at rest encryption is not strictly a requirement.
  – grg
  Aug 31 at 11:01
  
  

  
  
  
  

add a comment | 

up vote
1
down vote

up vote
1
down vote

One of the most important SQL Server 2016 features required by xDB is always encrypted which provides data at rest encryption. It's supported by MongoDB in Sitecore 8 xDB while SQL Server 2016 provides the same feature for Sitecore 9 xDB.

As a side note, SQL Server 2016 also added support for JSON, but xDB does not really use JSON data type in SQL.

share|improve this answer

edited Aug 31 at 11:05

answered Aug 31 at 10:03

grg

1,119111

One of the most important SQL Server 2016 features required by xDB is always encrypted which provides data at rest encryption. It's supported by MongoDB in Sitecore 8 xDB while SQL Server 2016 provides the same feature for Sitecore 9 xDB.

As a side note, SQL Server 2016 also added support for JSON, but xDB does not really use JSON data type in SQL.

share|improve this answer

edited Aug 31 at 11:05

answered Aug 31 at 10:03

grg

1,119111

share|improve this answer

share|improve this answer

edited Aug 31 at 11:05

edited Aug 31 at 11:05

edited Aug 31 at 11:05

answered Aug 31 at 10:03

grg

1,119111

answered Aug 31 at 10:03

grg

1,119111

answered Aug 31 at 10:03

grg

1,119111

1,119111

• 
  
  
  

  
  

  
  
  
  
  
  

  
  I think, Mongo DB also support the GDPR compliance, as most of the application still running on MongoDB with Sitecore
  – Ashish Bansal
  Aug 31 at 10:15
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @AshishBansal, yes, GDPR compliance can be achieved with both Mongo and SQL Server. I removed the note about GDPR as data at rest encryption is not strictly a requirement.
  – grg
  Aug 31 at 11:01
  
  

  
  
  
  

add a comment | 

• 
  
  
  

  
  

  
  
  
  
  
  

  
  I think, Mongo DB also support the GDPR compliance, as most of the application still running on MongoDB with Sitecore
  – Ashish Bansal
  Aug 31 at 10:15
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  @AshishBansal, yes, GDPR compliance can be achieved with both Mongo and SQL Server. I removed the note about GDPR as data at rest encryption is not strictly a requirement.
  – grg
  Aug 31 at 11:01
  
  

  
  
  
  

I think, Mongo DB also support the GDPR compliance, as most of the application still running on MongoDB with Sitecore
– Ashish Bansal
Aug 31 at 10:15

I think, Mongo DB also support the GDPR compliance, as most of the application still running on MongoDB with Sitecore
– Ashish Bansal
Aug 31 at 10:15

@AshishBansal, yes, GDPR compliance can be achieved with both Mongo and SQL Server. I removed the note about GDPR as data at rest encryption is not strictly a requirement.
– grg
Aug 31 at 11:01

@AshishBansal, yes, GDPR compliance can be achieved with both Mongo and SQL Server. I removed the note about GDPR as data at rest encryption is not strictly a requirement.
– grg
Aug 31 at 11:01

add a comment | 

 

draft saved

draft discarded

 

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f13635%2fwhy-sitecore-9-xdb-on-sql-server-2016%23new-answer', 'question_page');

);

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Sign up or log in

StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name Email

Name Email

Name

Email

Name Email

Name

Email