Skip to content

Add support for elastic pool and schedule time in Sql server upgrade #652

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 29, 2015
Merged

Add support for elastic pool and schedule time in Sql server upgrade #652

merged 2 commits into from
Jul 29, 2015

Conversation

hungmai-msft
Copy link
Contributor

Add the parameter for elastic pool in Start-AzureSqlServerUpgrade.
Return the schedule time of the upgrade (in case of forced upgrade) to customer in Get-AzureSqlServerUpgrade.
Modified tests and session records run on production (instead of on staging environment as existing session records)

Return both Status and ScheduleAfter time for Get-Upgrade cmdlet
Add session records run on production environment.
Replace TestServerUpgradeWithRecommnededDatabase with new test TestServerUpgradeWithUpgradeHint
@azuresdkci
Copy link

Can one of the admins verify this patch?

@azurecla
Copy link

Hi @hungmai-msft, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!


It looks like you're working at Microsoft (hungmai). If you're full-time, we DON'T require a contribution license agreement.



If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@hovsepm
Copy link
Contributor

hovsepm commented Jul 28, 2015

@azuresdkci add to whitelist

hovsepm pushed a commit that referenced this pull request Jul 29, 2015
Add support for elastic pool and schedule time in Sql server upgrade
@hovsepm hovsepm merged commit 898dff5 into Azure:dev Jul 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants