Sfrgttk

Microtypography protrusion with Polish quotation marks

Am I correct in stating that the study of topology is purely theoretical?

Boss asked me to sign a resignation paper without a date on it along with my new contract

Crack the bank account's password!

What is the wife of a henpecked husband called?

What can I do to encourage my players to use their consumables?

How do you get out of your own psychology to write characters?

Is there a way to not have to poll the UART of an AVR?

Why is the "Domain users" group missing from this Powershell AD Query?

"Starve to death" Vs. "Starve to the point of death"

If angels and devils are the same species, why would their mortal offspring appear physically different?

Memory usage: #define vs. static const for uint8_t

Can you determine if focus is sharp without diopter adjustment if your sight is imperfect?

Renting a 2CV in France

Can we "borrow" our answers to populate our own websites?

Can a player sacrifice a creature after declaring that creature as blocker while taking lethal damage?

Why do neural networks need so many training examples to perform?

How much mayhem could I cause as a fish?

How do I prevent a homebrew Grappling Hook feature from trivializing Tomb of Annihilation?

Does an Eldritch Knight's Weapon Bond protect him from losing his weapon to a Telekinesis spell?

What's after EXPSPACE?

In harmony: key or the flow?

Coworker asking me to not bring cakes due to self control issue. What should I do?

What is a good reason for every spaceship to carry a weapon on board?

Certifying New Versions of SQL Server

SQL Server Version - are hotfixes for previous versions implied?Use Older Versions Of SQL Server Databases With 2012?Count duplicate versions of databases (SQL Server 2008 R2)Is Query Performance different for different versions of SQL Server?SQL Server Service Broker Compatability across versions?Safest way to uninstall the previous SQL Server versionsData sync from different SQL Server versions databasesReplication between two different SQL Server versionsRun SQL Server 2016 side-by-side with older versions?Moving Databases between Instances of different Versions of SQL Server

2

1

I manage development teams that support a legacy app with a SQLServer backend. The app is deployed on-premise so our customers maybe run any version SQLServer (minimum 2008).

We have an on-going challenge of certifying that our app runs on new versions of SQLServer or any new service pack. It's very time consuming for our QA to run a full regression of our suite of products so I'm wondering if anyone faces the same challenge and has found another way to certify new releases of SQLServer as they come out.

We've though of turning on profiler and then hammering the app to capture SQL and just replay that on a new SQLServer instance with the new version. Is there a better way?

BTW, we use a lot of SQL features such as triggers, procs, views, defaults etc.

Thx

sql-server

share|improve this question

asked Nov 17 '18 at 1:14

sisdogsisdog

1112

add a comment | 

2

1

I manage development teams that support a legacy app with a SQLServer backend. The app is deployed on-premise so our customers maybe run any version SQLServer (minimum 2008).

We have an on-going challenge of certifying that our app runs on new versions of SQLServer or any new service pack. It's very time consuming for our QA to run a full regression of our suite of products so I'm wondering if anyone faces the same challenge and has found another way to certify new releases of SQLServer as they come out.

We've though of turning on profiler and then hammering the app to capture SQL and just replay that on a new SQLServer instance with the new version. Is there a better way?

BTW, we use a lot of SQL features such as triggers, procs, views, defaults etc.

Thx

sql-server

share|improve this question

asked Nov 17 '18 at 1:14

sisdogsisdog

1112

add a comment | 

I manage development teams that support a legacy app with a SQLServer backend. The app is deployed on-premise so our customers maybe run any version SQLServer (minimum 2008).

We have an on-going challenge of certifying that our app runs on new versions of SQLServer or any new service pack. It's very time consuming for our QA to run a full regression of our suite of products so I'm wondering if anyone faces the same challenge and has found another way to certify new releases of SQLServer as they come out.

We've though of turning on profiler and then hammering the app to capture SQL and just replay that on a new SQLServer instance with the new version. Is there a better way?

BTW, we use a lot of SQL features such as triggers, procs, views, defaults etc.

Thx

sql-server

share|improve this question

asked Nov 17 '18 at 1:14

sisdogsisdog

1112

share|improve this question

asked Nov 17 '18 at 1:14

sisdogsisdog

1112

share|improve this question

asked Nov 17 '18 at 1:14

sisdogsisdog

1112

asked Nov 17 '18 at 1:14

sisdogsisdog

1112

asked Nov 17 '18 at 1:14

sisdogsisdog

1112

1 Answer
1

active

oldest

votes

0

_{Answers originally left as comments}

I think you identified it in your question, regression testing. You maybe able to thin down the testing to just corner cases of the functionality. However if you are looking at more than “does it run” and wanting to test “how well does this run” a full test maybe your best option. – Aaron

To me, this is less of a question about the database, and more of an issue with your regression testing. You may want to explore ways to make your regression testing less labor intensive. – AMtwo

Also there aren’t that many things that work in 2008 and break in newer versions; the exceptions are limited to lists documented on Microsoft’s site, like this one for SQL Server 2016. So outside of those items, you should generally expect that moving to a new version should just work. Performance testing is something completely different, of course, and there aren’t any magic shortcuts aside from testing. Baselines are a good start. – Aaron Bertrand

share|improve this answer

answered 11 mins ago

Comment ConverterComment Converter

1,3071325

add a comment | 

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
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',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
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

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f222766%2fcertifying-new-versions-of-sql-server%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

0

_{Answers originally left as comments}

I think you identified it in your question, regression testing. You maybe able to thin down the testing to just corner cases of the functionality. However if you are looking at more than “does it run” and wanting to test “how well does this run” a full test maybe your best option. – Aaron

To me, this is less of a question about the database, and more of an issue with your regression testing. You may want to explore ways to make your regression testing less labor intensive. – AMtwo

Also there aren’t that many things that work in 2008 and break in newer versions; the exceptions are limited to lists documented on Microsoft’s site, like this one for SQL Server 2016. So outside of those items, you should generally expect that moving to a new version should just work. Performance testing is something completely different, of course, and there aren’t any magic shortcuts aside from testing. Baselines are a good start. – Aaron Bertrand

share|improve this answer

answered 11 mins ago

Comment ConverterComment Converter

1,3071325

add a comment | 

0

_{Answers originally left as comments}

I think you identified it in your question, regression testing. You maybe able to thin down the testing to just corner cases of the functionality. However if you are looking at more than “does it run” and wanting to test “how well does this run” a full test maybe your best option. – Aaron

To me, this is less of a question about the database, and more of an issue with your regression testing. You may want to explore ways to make your regression testing less labor intensive. – AMtwo

Also there aren’t that many things that work in 2008 and break in newer versions; the exceptions are limited to lists documented on Microsoft’s site, like this one for SQL Server 2016. So outside of those items, you should generally expect that moving to a new version should just work. Performance testing is something completely different, of course, and there aren’t any magic shortcuts aside from testing. Baselines are a good start. – Aaron Bertrand

share|improve this answer

answered 11 mins ago

Comment ConverterComment Converter

1,3071325

add a comment | 

_{Answers originally left as comments}

I think you identified it in your question, regression testing. You maybe able to thin down the testing to just corner cases of the functionality. However if you are looking at more than “does it run” and wanting to test “how well does this run” a full test maybe your best option. – Aaron

To me, this is less of a question about the database, and more of an issue with your regression testing. You may want to explore ways to make your regression testing less labor intensive. – AMtwo

Also there aren’t that many things that work in 2008 and break in newer versions; the exceptions are limited to lists documented on Microsoft’s site, like this one for SQL Server 2016. So outside of those items, you should generally expect that moving to a new version should just work. Performance testing is something completely different, of course, and there aren’t any magic shortcuts aside from testing. Baselines are a good start. – Aaron Bertrand

share|improve this answer

answered 11 mins ago

Comment ConverterComment Converter

1,3071325

share|improve this answer

answered 11 mins ago

Comment ConverterComment Converter

1,3071325

answered 11 mins ago

Comment ConverterComment Converter

1,3071325

answered 11 mins ago

Comment ConverterComment Converter

1,3071325