-- 'Ӈ耇' was found in the text of this event.
-- The text has been replaced with this comment for security reasons.
At first, I feared a Chinese Injection Attack, but after a little digging around, I was able to reproduce it by running a trace, then stopping the traced SQL Service while profiler was still running the trace. It's apparently a built in error code.
I thought I had seen similar behavior in the past around queries that include the word "PASSWORD" in them, so I started playing around to see if I remembered correctly. It turns out my recollection wasn't perfect.
When you run a security statement that might contain a login's password, SQL Profiler will remove the TextData from the event.
Here are a few such statements where TextData is stripped:
sp_password
CREATE LOGIN
ALTER LOGIN
Of course, before rediscovering this, I had already run a statement using the word "PASSWORD" and profiler happily displayed my query text. I thought I'd share, not because of the query is so profound, but because I wrote it simply for the joy of writing it.
CREATE DATABASE PASSWORD;
go
USE PASSWORD;
go
CREATE SCHEMA PASSWORD;
go
CREATE TABLE PASSWORD.PASSWORD (PASSWORD SYSNAME);
go
INSERT PASSWORD.PASSWORD.PASSWORD (PASSWORD) VALUES ('PASSWORD');
go
CREATE INDEX PASSWORD ON PASSWORD.PASSWORD.PASSWORD (PASSWORD);
go
SELECT PASSWORD.PASSWORD.PASSWORD.PASSWORD
FROM PASSWORD.PASSWORD.PASSWORD WITH(INDEX(PASSWORD))
WHERE PASSWORD.PASSWORD.PASSWORD.PASSWORD = PASSWORD.PASSWORD.PASSWORD.PASSWORD;
go
DROP TABLE PASSWORD.PASSWORD;
go
DROP SCHEMA PASSWORD;
GO
USE TEMPDB;
go
DROP DATABASE PASSWORD;
GO
It's also amazingly blue because nearly every word is reserved. If you'd like to play with it, it should run for you on any system that doesn't already have a database named "PASSWORD"
I hope you also find such light-hearted simple ways to enjoy the tools you work with.
No comments:
Post a Comment