Database

DROP PROCEDURE IF EXISTS tgc.UpdateCustomerBalance;
CREATE PROCEDURE tgc.`UpdateCustomerBalance`(customerId varchar(50), cost Decimal(8,2))
BEGIN
UPDATE Customers SET Balance = Balance - cost WHERE CustomerId = customerId;
END;

try
            {
                using (var context = new Db_Entities())
                {
                object[] parameters =
                {
                    new MySql.Data.MySqlClient.MySqlParameter("@customerId", customerId),
                    new MySql.Data.MySqlClient.MySqlParameter("@cost", cost)
                };
                  
                await context.Database.ExecuteSqlCommandAsync("UpdateCustomerBalance @customerId,@cost", parameters);
                }
            }
            catch (Exception e)
            {
                throw;
            }

"Message": "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'UpdateCustomerBalance 'xyz',0.03' at line 1",

await context.Database.ExecuteSqlCommandAsync("UPDATE Customers SET Balance = Balance - " + cost + " WHERE CustomerId = '" + customerId + "'");

SELECT DISTINCT
b.event_id AS a,
b.user_ID AS a,
b.date AS a,
b.Time AS a
FROM quadrantids2017 AS a
JOIN quadrantids2017 AS b
WHERE a.`date` = b.`date`

AND a.user_ID != b.user_ID
AND time_to_sec(a.`Time`) - time_to_sec(b.`Time`) BETWEEN -30 AND 30

CREATE DATABASE CIDB COLLATE Latin1_General_CI_AI;
GO
USE CIDB;
CREATE TABLE TEST (ID INTEGER);

SELECT * FROM TEST;
select * FROM TEST;
SELECT * FROM Test;
select * FROM Test;

:) --> Everything works like expected, MSSQL does not bother about "TEST" or "Test".

CREATE DATABASE CSDB COLLATE Latin1_General_CS_AI;
GO
USE CSDB;
CREATE TABLE TEST (ID INTEGER);

SELECT * FROM TEST;

Everyting up to here is working fine. But ...

   SELECT * FROM Test;

   ??--> fails with error message "Msg 208, Level 16, State 1, Line 1 Invalid object name 'Test'."

... obviously because the database is created "Sensitive".

What's really surprising for me, that the collation sequence now also
makes the SQL Language a case sensitive, not the language it self but
the objects (table-, field- names and I assume also constraint names).