Updated TableCreationScript for SQL Azure #114
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The TableCreationScript didn't have a clustered primary key on the MiniProfilers table, and would fail when used in SQL Azure. By adding the unused RowId column profiling can now be saved to SQL Azure. An additional unique index IX_MiniProfilers_Id has been added to replace the loss of the PK constraint on the Id column. See http://stackoverflow.com/a/14775721/495964
dixon
added a commit
that referenced
this pull request
Feb 8, 2013
Updated TableCreationScript for SQL Azure
|
Thanks, and thank you for answering that question :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've just been using MiniProfiler and setting it up to store the profile results in SQL Azure. I've used the latest TableCreationScript, but it failed because SQL Azure requires all tables to have a primary clustered index.
I also answered this question on stackoverflow while producing the solution.
The change still works on tradition SQL Server, which I use in development.