sql role assignment name must be a guid

Home » SQL Server GUID

SQL Server GUID

Summary : in this tutorial, you will learn about the SQL Server GUID and how to use the  NEWID()  function to generate GUID values.

Introduction to SQL Server GUID

All things in our world are numbered e.g., books have ISBNs, cars have VINs, and people have social security numbers (SSN).

The numbers, or identifiers, help us reference things unambiguously. For example, we can identify John Doe by using his unique social security number 123-45-6789 .

A globally unique identifier or GUID is a broader version of this type of ID numbers.

A GUID is guaranteed to be unique across tables, databases, and even servers.

In SQL Server, GUID is 16-byte binary data type, which is generated by using the NEWID() function:

If you execute the above statement several times, you will see different value every time. Here is one of them:

In SQL Server, the UNIQUEIDENTIFIER data type holds GUID values.

The following statements declare a variable with type UNIQUEIDENTIFIER and assign it a GUID value generated by the NEWID() function.

Here is the output:

Using SQL Server GUID as primary key

Sometimes, it prefers using GUID values for the primary key column of a table than using integers.

Using GUID as the primary key of a table brings the following advantages:

• GUID values are globally unique across tables, databases, and even servers. Therefore, it allows you to merge data from different servers with ease.
• GUID values do not expose the information so they are safer to use in public interface such as a URL. For example, if you have the URL https://www.example.com/customer/100/ URL, it is not so difficult to find that there will have customers with id 101, 102, and so on. However, with GUID, it is not possible: https://www.example.com/customer/F4AB02B7-9D55-483D-9081-CC4E3851E851/

Besides these advantages, storing GUID in the primary key column of a table has the following disadvantages:

• GUID values (16 bytes) takes more storage than INT (4 bytes) or even BIGINT (8 bytes)
• GUID values make it difficult to troubleshoot and debug, comparing WHERE id = 100 with WHERE id = 'F4AB02B7-9D55-483D-9081-CC4E3851E851' .

SQL Server GUID example

First, create a new table named customers in the marketing schema:

Second, insert new rows into the marketing.customers table:

Third, query data from the marketing.customers table:

In this tutorial, you have learned about the SQL Server GUID and how to use the NEWID() function to generate GUID values.

• AnsibleFest
• Webinars & Training

• Collection Index
• Collections in the Azure Namespace
• Azure.Azcollection
• azure.azcollection.azure_rm_roleassignment module – Manage Azure Role Assignment

azure.azcollection.azure_rm_roleassignment module – Manage Azure Role Assignment 

This module is part of the azure.azcollection collection (version 1.19.0).

You might already have this collection installed if you are using the ansible package. It is not included in ansible-core . To check whether it is installed, run ansible-galaxy collection list .

To install it, use: ansible-galaxy collection install azure.azcollection . You need further requirements to be able to use this module, see Requirements for details.

To use it in a playbook, specify: azure.azcollection.azure_rm_roleassignment .

New in azure.azcollection 0.1.2

Create and delete instance of Azure Role Assignment.

Requirements 

The below requirements are needed on the host that executes this module.

python >= 2.7

The host that executes this module must have the azure.azcollection collection installed via galaxy

All python packages listed in collection’s requirements-azure.txt must be installed via pip on the host that executes modules from azure.azcollection

Full installation instructions may be found https://galaxy.ansible.com/azure/azcollection

Parameters 

For authentication with Azure you can pass parameters, set environment variables, use a profile stored in ~/.azure/credentials, or log in before you run your tasks or playbook with az login .

Authentication is also possible using a service principal or Active Directory user.

To authenticate via service principal, pass subscription_id, client_id, secret and tenant or set environment variables AZURE_SUBSCRIPTION_ID, AZURE_CLIENT_ID, AZURE_SECRET and AZURE_TENANT.

To authenticate via Active Directory user, pass ad_user and password, or set AZURE_AD_USER and AZURE_PASSWORD in the environment.

Alternatively, credentials can be stored in ~/.azure/credentials. This is an ini file containing a [default] section and the following keys: subscription_id, client_id, secret and tenant or subscription_id, ad_user and password. It is also possible to add additional profiles. Specify the profile by passing profile or setting AZURE_PROFILE in the environment.

How to authenticate using the az login command.

Return Values 

Common return values are documented here , the following are the fields unique to this module:

Yunge Zhu(@yungezz)

Paul Aiton(@paultaiton)

Collection links 

• Issue Tracker
• Repository (Sources)

Search code, repositories, users, issues, pull requests...

Provide feedback.

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly.

To see all available qualifiers, see our documentation .

• Notifications

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

New-AzRoleAssignment "InvalidPrincipalId" "The Principal ID 'User' is not valid. Principal ID must be a GUID." #16627

brwilkinson commented Dec 13, 2021 • edited

Successfully merging a pull request may close this issue.

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

az role assignment

Manage role assignments.

az role assignment create

Create a new role assignment for a user, group, or service principal.

Create role assignment to grant the specified assignee the Reader role on an Azure virtual machine.

Create role assignment for an assignee with description and condition.

Create role assignment with your own assignment name.

Required Parameters

Role name or id.

Scope at which the role assignment or definition applies to, e.g., /subscriptions/0b1f6471-1bf0-4dda-aec3-111122223333, /subscriptions/0b1f6471-1bf0-4dda-aec3-111122223333/resourceGroups/myGroup, or /subscriptions/0b1f6471-1bf0-4dda-aec3-111122223333/resourceGroups/myGroup/providers/Microsoft.Compute/virtualMachines/myVM.

Optional Parameters

Represent a user, group, or service principal. supported format: object id, user sign-in name, or service principal name.

Use this parameter instead of '--assignee' to bypass Graph API invocation in case of insufficient privileges. This parameter only works with object ids for users, groups, service principals, and managed identities. For managed identities use the principal id. For service principals, use the object id and not the app id.

Use with --assignee-object-id to avoid errors caused by propagation latency in Microsoft Graph.

Condition under which the user can be granted permission.

Version of the condition syntax. If --condition is specified without --condition-version, default to 2.0.

Description of role assignment.

A GUID for the role assignment. It must be unique and different for each role assignment. If omitted, a new GUID is generetd.

Increase logging verbosity to show all debug logs.

Show this help message and exit.

Only show errors, suppressing warnings.

Output format.

JMESPath query string. See http://jmespath.org/ for more information and examples.

Name or ID of subscription. You can configure the default subscription using az account set -s NAME_OR_ID .

Increase logging verbosity. Use --debug for full debug logs.

az role assignment delete

Delete role assignments.

Delete role assignments. (autogenerated)

Space-separated role assignment ids.

Include assignments applied on parent scopes.

Use it only if the role or assignment was added at the level of a resource group.

Continue to delete all assignments under the subscription.

az role assignment list

List role assignments.

By default, only assignments scoped to subscription will be displayed. To view assignments scoped by resource or group, use --all .

Show all assignments under the current subscription.

List default role assignments for subscription classic administrators, aka co-admins.

Include extra assignments to the groups of which the user is a member(transitively).

az role assignment list-changelogs

List changelogs for role assignments.

The end time of the query in the format of %Y-%m-%dT%H:%M:%SZ, e.g. 2000-12-31T12:59:59Z. Defaults to the current time.

The start time of the query in the format of %Y-%m-%dT%H:%M:%SZ, e.g. 2000-12-31T12:59:59Z. Defaults to 1 Hour prior to the current time.

az role assignment update

Update an existing role assignment for a user, group, or service principal.

Update a role assignment from a JSON file.

Update a role assignment from a JSON string. (Bash)

Description of an existing role assignment as JSON, or a path to a file containing a JSON description.

Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback .

Submit and view feedback for

Additional resources