SQL 2005 Encryption

See reference for tutorial on SQL 2005 encryption...

References: http://www.sqlservercentral.com/articles/SQL+Server+2005+-+Security/sql2005symmetricencryption/2291/

SQL 2005 Performance Monitor Counter problem

Use this article below to manually increment the counter registry key.

Reference: http://msdn.microsoft.com/en-us/library/ms143215.aspx

SQL 2000 DTS Security

Some excerpts from link below:

• If you want to alter this default behavior and restrict the ability to create new or modify existing packages, you can modify permissions on the sp_add_dtspackage, sp_enum_dtspackages, and sp_get_dtspackage stored procedures in the MSDB database. The first one contains T-SQL code for creating DTS packages, the second one provides ability to list them and the third one is used for retrieving them. By removing permissions to run them from the public role, you can restrict these activities to specific fixed or custom database roles.
• Another possibility to secure packages saved to SQL Server or a Structured Storage file (but not to Meta Data Services or a Visual Basic file) is by assigning owner and user passwords. This is done from the DTS Designer interface, by selecting the Save As... item from the Package top level menu. In the resulting "Save DTS" Package dialog box, you can type in the owner and user password (note that you cannot set a user password without defining the owner password). An owner password secures opening and modifying the content of a package; knowledge of the user password allows its execution (you are prompted for them whenever you try to execute or open the package to which they were assigned). Keep in mind that there is no direct way to change these passwords. The only way to accomplish this is to save the package using a different name, then delete original package, and finally rename back the new one (this is clearly much more complicated than it should be).
• Each package has an owner, which is the login that created it (or saved an existing one to a new server - when transferring packages between computers). Identifying information is recorded in the syspackages table of the MSDB databases in the owner and owner_sid columns. Only package owners (and members of Sysadmin fixed server role) have the ability to alter packages and save them with the same name (they are still, however, required to provide passwords in order to open or execute their packages).

Reference: http://www.databasejournal.com/features/mssql/article.php/3404791/SQL-Server-2000-Security---Part-11---DTS-Security.htm

Sync-ing with iPhone

References: http://www.tipb.com/2008/07/07/switching-to-iphone-how-to-move-your-contacts-calendar-and-email-to-the-iphone-wait-a-thon/

Extracting Intel NIC drivers

The files listed below are for Windows XP* or Windows Server 2003*, 32-bit editions.

1. Download the latest driver package (PROWin32.exe) from Download Center.
2. Create a temporary folder for the extracted driver files. (Example: C:\Temporary)
3. Open an command-line prompt window, then go to the directory where the downloaded driver file was saved and enter “PROWin32.exe /s /e /f c:\Temporary”.
4. When the command prompt appears, the files have been extracted successfully.

Reference: http://www.intel.com/support/network/sb/CS-026658.htm

IIS 6 and Application Pools

Here is a nice explanation regarding IIS 6 application pools...

The 2nd one explains how to configure a new Application pool identity account.

Reference: http://www.developer.com/net/asp/article.php/2245511/IIS-and-ASPNET-The-Application-Pool.htm
http://support.microsoft.com/kb/832770

WBCOOP

I have registered to play in the PokerStars World Blogger Championship of Online Poker! The WBCOOP is a free online Poker tournament open to all Bloggers, so register on WBCOOP to play.

Registration code: 994146