Merge pull request #24695 from rwestMSFT/rw-1027-db-permissions-poster

Rename permissions poster filename to refresh the image

Author: Stacyrch140

azure-sql/database/logins-create-manage.md

@@ -147,7 +147,7 @@ After creating a user account in a database, either based on a login or as a con
   Create a custom database role using the [CREATE ROLE](/sql/t-sql/statements/create-role-transact-sql) statement. A custom role enables you to create your own user-defined database roles and carefully grant each role the least permissions necessary for the business need. You can then add users to the custom role. When a user is a member of multiple roles, they aggregate the permissions of them all.
 - **Grant permissions directly**
 
-  Grant the user account [permissions](/sql/relational-databases/security/permissions-database-engine) directly. There are over 100 permissions that can be individually granted or denied in SQL Database. Many of these permissions are nested. For example, the `UPDATE` permission on a schema includes the `UPDATE` permission on each table within that schema. As in most permission systems, the denial of a permission overrides a grant. Because of the nested nature and the number of permissions, it can take careful study to design an appropriate permission system to properly protect your database. Start with the list of permissions at [Permissions (Database Engine)](/sql/relational-databases/security/permissions-database-engine) and review the [poster size graphic](/sql/relational-databases/security/media/database-engine-permissions.png) of the permissions.
+  Grant the user account [permissions](/sql/relational-databases/security/permissions-database-engine) directly. There are over 100 permissions that can be individually granted or denied in SQL Database. Many of these permissions are nested. For example, the `UPDATE` permission on a schema includes the `UPDATE` permission on each table within that schema. As in most permission systems, the denial of a permission overrides a grant. Because of the nested nature and the number of permissions, it can take careful study to design an appropriate permission system to properly protect your database. Start with the list of permissions at [Permissions (Database Engine)](/sql/relational-databases/security/permissions-database-engine) and review the [poster size graphic](/sql/relational-databases/security/media/database-engine-permissions-small.png) of the permissions.
 
 ## Using groups
 

…missions/database-engine-permissions.png …ns/database-engine-permissions-small.pngdocs/includes/media/database-engine-permissions/database-engine-permissions.png renamed to docs/includes/media/database-engine-permissions/database-engine-permissions-small.png docs/includes/media/database-engine-permissions/database-engine-permissions.png renamed to docs/includes/media/database-engine-permissions/database-engine-permissions-small.png

@@ -8,4 +8,4 @@ ms.topic: include
 ---
 The following image shows the permissions and their relationships to each other. Some of the higher level permissions (such as `CONTROL SERVER`) are listed many times. In this article, the poster is far too small to read. You can download the full-sized **[Database Engine Permissions Poster](https://aka.ms/sql-permissions-poster)** in PDF format.
 
-:::image type="content" source="../media/database-engine-permissions/database-engine-permissions.png" alt-text="A screenshot from the Database Engine permissions PDF.":::
+:::image type="content" source="../media/database-engine-permissions/database-engine-permissions-small.png" alt-text="A screenshot from the Database Engine permissions PDF.":::