New answers tagged

0

When declaring HEX strings such as UUIDs, or when declaring other strings with limited character set needs, such as country_code, postal_code, zip_code, etc, declare them to be CHARACTER SET ascii. It can be applied just to the column, letting the rest of your columns be utf8mb4 or whatever. And be consistent between tables so that JOIN works efficient. ...


0

Stored Procedures also have a collation defined Here is mysql.proc mysql> show create table mysql.proc\G *************************** 1. row *************************** Table: proc Create Table: CREATE TABLE `proc` ( `db` char(64) CHARACTER SET utf8 COLLATE utf8_bin NOT NULL DEFAULT '', `name` char(64) NOT NULL DEFAULT '', `type` ...


4

While @Max is correct about a) the root cause of this error (collation of restored msdb database does not match the server's default collation, which is used to set the collation of the name field in master.sys.sysdbreg -- the actual source of the name field in sys.databases), and b) that ideally you would rebuild msdb to have a collation matching the ...


2

In general collations can be persuaded to match one another. See my comments at: Contained DB Collation error Perhaps the comments on collation, particulary the CATALOG_DEFAULT, may provide you some assistance: The database collation is retained, but is only used as the default collation for user data. A new keyword, CATALOG_DEFAULT, is available in the ...


7

The sysdac_instances view is defined as follows: CREATE VIEW [dbo].[sysdac_instances] AS SELECT -- this must be locked down because we use instance_id visability as a security gate case when (dbo.fn_sysdac_is_currentuser_sa() = 1) then dac_instances.instance_id when sd.owner_sid = SUSER_SID() then ...



Top 50 recent answers are included