A self-generated certificate was successfully loaded for encryption?

Log shows (on SS2005)
“A self-generated certificate was successfully loaded for encryption”

No encryption is used. Properties of Protocol for MSSQLSERVER shows no for Force Encryption, certificates are empty

How, why, where from and what for does it get and load self-generated certificate?

This certificate refers to a self-generated certificate used as a “best-effort” mechanism to protect the SQL login information (including password) when using SQL authentication.

By default this self-signed certificate should only affect the login information and only when using SQL authentication (no penalty for using Windows auth).

Pleaes be aware that because this is a self-signed certificate it is subject to an active attack (i.e. MiM), but it provides a better defense against a passive attacker (“sniffing” passwords) than SQL Server 2000.

For more information refer to BOL:

http://blogs.msdn.com/sql_protocols/archive/2005/11/10/491563.aspx

http://blogs.msdn.com/sql_protocols/archive/2005/10/11/479869.aspx

I hop this information helps

-Raul Garcia

SDE/T

SQL Server Engine

A script to get properties of full text catalog?

Hey, all--

My organization is having a problem with MS-SQL's sporadically stopping full-text catalog population on one of our databases. New content is added to that database constantly, so we have an incremental population schedule set up to update the index once an hour. This works fine for a while and then stops for no apparent reason; we don't notice it having stopped until someone comes along to tell us they can't find something.

We've been trying different things to fix it, but in the meanwhile, is there a way to expose the properties (particularly the Last Population Date) of a full-text catalog to an outside script, so that we could incorporate a check of the catalog status into our daily server health scripts? Or, alternatively, a way to have the database server send out an email when the last incremental update is more than an hour old? It's no good to have our users being the ones to tell us when the indexing has failed.

Thanks much.Hello,

Try

use DatabaseName
select FulltextCatalogProperty(N'CatalogName', N'PopulateCompletionAge')

Its in seconds since 12:00:00 A.M., January 1, 1990.

I'll get you more info after i walk downstairs and get some starbucks :)|||Oh, that's perfect. Thanks so much.

For the reference of future readers of this topic, that first param is actually the catalog name, not the database name. Full Microsoft documentation is here: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_fa-fz_7x15.asp . It's amazing what you can find when you know what you're looking for... thanks again!|||Select dateadd(s,FulltextCatalogProperty(N'CatalogName', N'PopulateCompletionAge'),'1/1/1990')

Alot of times, I'll do a incremental right after the insert. That will only be helpful in certain situations.

Thanks for the note on the Catalog name. It looked fishy but I didnt look into it. I guess my catalog name is the same as my database name ;)