One way you could do this (but you definitely should not do this)
is by changing the database collation to be case sensitive.
This only works if your table is in fact written as
Consider this example
CREATE DATABASE TEMP2
CREATE TABLE [dbo].[SysMessages](
[id] [int] NULL,
[message] [varchar](255) NULL
) ON [PRIMARY]
ALTER DATABASE TEMP2 COLLATE Latin1_General_CS_AS;
Query with case sensitive collation
SELECT * FROM [dbo].[SysMessages]
Query with case insensitive collation
ALTER DATABASE TEMP2 COLLATE Latin1_General_CI_AS;
SELECT * FROM [dbo].[SysMessages];
error severity dlevel description msglangid
21 20 0 Warning: Fatal error %d occurred at %S_DATE. Note the error and time, and contact your system administrator. 1033
101 15 0 Query not allowed in Waitfor. 1033
102 15 0 Incorrect syntax near '%.*ls'. 1033
Again, this is only to make the case that you could, but you definitely should not do this.
Trying to change the collation can give you errors like this one:
The statistics '...' is dependent on database collation. The database collation cannot be changed if a schema-bound object depends on it. Remove the dependencies on the database collation and then retry the operation.
I tried some other stuff like synonyms and denying select on the
sysmessages dmv to my login but these did not work.