Viewing 15 posts - 631 through 645 (of 821 total)
-- to see all bad attempts
SELECT l.name, loginproperty(l.name, 'BadPasswordTime')
FROM sys.syslogins l
May 26, 2011 at 2:01 am
In sql2005, I tried with other logins than sa and I get always the following:
1900-01-01 02:00:00.000
Step 1: bad password attempt
Step 2: correct login
I run the query: SELECT loginproperty('carlo', 'badpasswordtime')
The result:...
May 26, 2011 at 1:50 am
Koen Verbeeck (5/16/2011)
And the explanation doesn't mention why inserting NULL in another string doesn't result in NULL, but in an empty space instead.
I am curious: bol does not mention the...
May 17, 2011 at 1:14 am
SQLRNNR (5/4/2011)
I like it too. I also like that the R2 doc seems better written on this topic than the SQL 2008 doc
I agree with you! 😀
May 5, 2011 at 12:52 am
In addition, the administrator should disable in AD and kill all disabled-user's connections.
April 22, 2011 at 1:20 am
It's a good habit always to specify precision and scale because of changing default in future releases.
April 18, 2011 at 1:13 am
Steve Jones - SSC Editor (4/12/2011)
You do not have to post to get points...
April 13, 2011 at 2:57 am
Thank you very much for this beautiful qotd.
It's unbelievable, but true, only new types DATE and DATETIME2 work in any case.
April 13, 2011 at 1:29 am
The correct answer is "None of the above"
http://msdn.microsoft.com/en-us/library/ms188783.aspx
Tables must be referenced by two-part names, schema.tablename, in the view definition.
I want back my points.
March 30, 2011 at 3:47 am
In these days, I am changing collate on third party's database.
March 23, 2011 at 2:01 am
Unbelievable, but true!
Thank you for qotd and a clear explanation!
March 21, 2011 at 2:01 am
tommyh (3/18/2011)
I was hoping that SQL would fail on the last comma in the create table part. But SQL was just as happy to create a table like that./T
I...
March 18, 2011 at 2:20 am
Viewing 15 posts - 631 through 645 (of 821 total)