Wednesday, March 21, 2012

Outlook Public folder: How to set up the AutoForward Rule on Public Folder


You must have Owner (Owner permission: With Owner permission you can create, read, modify, and delete all items and files and create subfolders. As folder owner, you can change the permission level that others have for the folder. This permission does not apply to delegates.) permission for a public folder to create or modify rules (rule: One or more automatic actions taken on e-mail messages and meeting requests that meet certain conditions, along with any exceptions to those conditions. Rules are also referred to as filters.) for it.

  1. In the Folder List (Folder List: Displays the folders available in your mailbox. To view subfolders, click the plus sign (+) next to the folder. If the Folder List is not visible, on the Go menu, click Folder List.), in the Navigation Pane (Navigation Pane: The column on the left side of the Outlook window that includes panes such as Shortcuts or Mail and the shortcuts or folders within each pane. Click a folder to show the items in the folder.), right-click the public folder you want to create or modify rules for, and then click Properties on the shortcut menu.
  2. Click the Administration tab.
  3. Click Folder Assistant.
    Do either of the following:
  4. To create a rule, click Add Rule.
  5. To modify an existing rule, click a rule in the list, and then click Edit Rule.
    Enter the conditions that the item must meet for the action to occur. For more conditions, click Advanced.
    Under Perform these actions, select the options you want.

Monday, March 19, 2012

Quick way of getting Date and Time appended on filename in DOS Batch


echo off

set filename=F:\Sivaprasad\Error%time:~0,2%%time:~3,2%%time:~6,2%_%date:~-10,2%%date:~-7,2%%date:~-4,4%.txt

echo  %filename%

DOS Batch file To search string in given file



To Search the given files under current directory for given strings. If anything found to be written to a file.

Sample Screen:



Main Script: CHK_Error.bat

@echo off

set fname=
set filename=
set yyyymmdd=
set hhmm=

IF %1. NEQ . (set fname="C:\Accounts\CalWIN\Build\SQLServer\DOS_Batch\%1*.lst") ELSE ( GOTO _Usage )

for /F "tokens=2-4 delims=/ " %%i in ('date /t') do set yyyymmdd=%%k%%i%%j

for /F "tokens=1-2 delims=: " %%l in ('time /t') do set hhmm=%%l%%m

set filename=Error_%yyyymmdd%%hhmm%.txt

echo "Error Log file name is : " %filename%

echo "files to be searched : " %fname%

findstr /i /n /g:search.txt  %fname% > %filename%

if %errorlevel% == 0 (GOTO :_Error_Found ) else  (
Echo  **  No Errors found    **
Goto :END )

notepad %filename%
Goto :END

echo " Usage is chkerrors.bat <filestring>

@echo on



Input Files: file1.lst


st messgae



error 121




msg 128, 9341353513

Input Files: file2.lst

test messgae

error 121




msg 128, 9341353513

Tuesday, March 13, 2012

ZoomIt screen zoom and annotation tool for presentation


ZoomIt is screen zoom and annotation tool for technical presentations that include application demonstrations. ZoomIt runs unobtrusively in the tray and activates with customizable hotkeys to zoom in on an area of the screen, move around while zoomed, and draw on the zoomed image.

Enjoy using this tool on your presentation. It can be downloaded from

Sunday, March 11, 2012

Database Development Lifecycle


SQL Server Database Development with

Visual Studio 2010

1. Establish Project Environment

2. Perform Isolated, iterative development

3. Build the Project

4. Deploy from Project environment

Establish the Project Environment

The following illustration shows how the team member who performs the role of the database administrator (DBA) establishes the project environment.

The DBA starts by creating a database project and importing the database schema from the production database. The DBA then can create a data generation plan to create test data for the isolated development environments. Finally, the DBA checks the database project into version control, which makes it available to the team

Perform Isolated, iterative Development


Each database professional synchronizes their development environment to version control. They can check out files as they are changed and develop and test those changes in isolation. Changes made to their copy of the database project are deployed only to their isolated development environment. After a team member generates realistic test data and runs unit tests against a private copy of the database, the team member checks the changes into version control. Other team members obtain tested changes from version control.

Generate Daily Builds of the Project

how the build cycle works for database projects


The daily build is generated by synchronizing to the most recent tested version of the database project in the version control system. That build can be deployed to a test database where unit tests are run against generated test data.

Deployment from Project Environment

how the DBA can deploy a version of the database project into production


When it is time to deploy a version of the database to production, the DBA synchronizes to a label from the version control system. The DBA retrieves matching files for the database project, related scripts, and tests. Next, the DBA builds the .dbschema file. From the .dbschema file, the DBA generates the deployment script, makes manual modifications as needed, and does a test deployment to the staging server. The DBA iterates this process until the script is ready to be deployed to the production server. If the DBA made changes to the schema or to the pre-deployment or post-deployment scripts, those changes will be checked back in to version control.