Tuesday, April 7, 2009

How to identify your SQL Server version and edition

Reference :- Article ID: 321185 - Last Review: December 22, 2008 - Revision: 12.0

This article describes how to identify your current Microsoft SQL Server version number and the corresponding product or service pack level. It also describes how to identify the specific edition if you are using Microsoft SQL Server 2000 or Microsoft SQL Server 7.0.

How to determine which version of SQL Server 2005 is running
To determine which version of Microsoft SQL Server 2005 is running, connect to SQL Server 2005 by using SQL Server Management Studio, and then run the following Transact-SQL statement:

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

The following results are returned:
The product version (for example, 9.00.1399.06).
The product level (for example, RTM).
The edition (for example, Enterprise Edition).


For example, the results resemble the following:
9.00.1399.06 RTM Enterprise Edition

The following table lists the Sqlservr.exe version number:
Release Sqlservr.exe
RTM 2005.90.1399
SQL Server 2005 Service Pack 1 2005.90.2047
SQL Server 2005 Service Pack 2 2005.90.3042
SQL Server 2005 Service Pack 3 2005.90.4035

How to determine which version of SQL Server 2000 is running
To determine which version of SQL Server 2000 is running, connect to SQL Server 2000 by using Query Analyzer, and then run the following code:

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

The following results are returned:
The product version (for example, 8.00.534).
The product level (for example, "RTM" or "SP2").
The edition (for example, "Standard Edition"). 

For example, the results resemble the following:
8.00.534 SP2 Standard Edition

The following table lists the Sqlservr.exe version number:
Release Sqlservr.exe
RTM 2000.80.194.0
SQL Server 2000 SP1 2000.80.384.0
SQL Server 2000 SP2 2000.80.534.0
SQL Server 2000 SP3 2000.80.760.0
SQL Server 2000 SP3a 2000.80.760.0
SQL Server 2000 SP4 2000.8.00.2039

How to determine which version of SQL Server 7.0 is running
To determine which version of SQL Server 7.0 is running, connect to SQL Server 7.0 by using Query Analyzer, and then run the following code:

SELECT @@VERSION

The results resemble the following:
Microsoft SQL Server 7.00 - 7.00.623 (Intel X86)
Nov 27 1998 22:20:07
Copyright (c) 1988-1998 Microsoft Corporation
Desktop Edition on Windows NT 5.1 (Build 2600: )

Note In this example, the version number is 7.00.623.

Use the version number in the following table to identify the product or service pack level:
Version Number Service Pack
7.00.1063 SQL Server 7.0 Service Pack 4 (SP4)
7.00.961 SQL Server 7.0 Service Pack 3 (SP3)
7.00.842 SQL Server 7.0 Service Pack 2 (SP2)
7.00.699 SQL Server 7.0 Service Pack 1 (SP1)
7.00.623 SQL Server 7.0 RTM (Release To Manufacturing)

If the version number that is reported by @@VERSION is not listed in this table, SQL Server is running with a hotfix or a security update build. For example, if @@VERSION reports a version number of 7.00.859, you are running SQL Server 7.0 SP2 with a hotfix installed. The version number increases with each new version of the Sqlservr.exe executable file. 
See to the Readme.txt file for your hotfix or security update for more information.

How to determine which version of SQL Server 6.5 is running
To determine which version of Microsoft SQL Server 6.5 is running, connect to SQL Server 6.5 by using Isql_w, and then run the following code:

SELECT @@VERSION

Use the version number in the following table to identify the product or service pack level:
Version Number Service Pack
6.50.479 SQL Server 6.5 Service Pack 5a (SP5a) Update
6.50.416 SQL Server 6.5 Service Pack 5a (SP5a)
6.50.415 SQL Server 6.5 Service Pack 5 (SP5)
6.50.281 SQL Server 6.5 Service Pack 4 (SP4)
6.50.258 SQL Server 6.5 Service Pack 3 (SP3)
6.50.240 SQL Server 6.5 Service Pack 2 (SP2)
6.50.213 SQL Server 6.5 Service Pack 1 (SP1)
6.50.201 SQL Server 6.5 RTM

If the version number that is reported by @@VERSION is not listed in this table, SQL Server is running with a hotfix or a security update build. The version number increases with each new version of the Sqlservr.exe executable file. See to the Readme.txt file for your hotfix or security update for more information.

How to determine which edition of SQL Server is running
If you are not sure about what edition of SQL Server that you are running, the last line of output that is returned by @@VERSION reports the edition to which you have connected. The example that is used in this article is the Standard Edition of SQL Server 2000 on Windows NT 5.0 (Build 2195: Service Pack 2).

Note The build and service pack information that is provided earlier is for the operating system, not for SQL Server.
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 2)

Thursday, April 2, 2009

Make your Friends Fool through VBS file.

 If you want to make someone fool using Outlook then here is the best way.

We have written a VBS file that simply opens the outlook creates a new mail, enters the TO recipient, writes something in the subject and email contents and send it. 

If you are thinking that it is just a joke fro April month then you are totally wrong. Yes this is possible. How to create this vbs file? Please go through the steps:-

1.       Open a notepad and write the code given below.

 

Set WshShell = WScript.CreateObject("WScript.Shell")

 

WshShell.Run "Outlook"

 

WScript.Sleep 2500 ' Give Notepad some time to load

 

WshShell.SendKeys "^{n}"

 

WScript.Sleep 1000

 

WshShell.SendKeys "abcd@abcd.xyz"

 

WshShell.SendKeys "{TAB}"

 

WshShell.SendKeys "{TAB}"

 

WshShell.SendKeys "{TAB}"

 

WshShell.SendKeys "{TAB}"

 

WshShell.SendKeys "{TAB}"

 

WScript.Sleep 200

 

WshShell.SendKeys " Hi ABC, I accept that I am a FOOL ...and you made a fool out of me today ... I don’t think God planted brains in my head!!!!...otherwise I would have checked out the code first! you are great. hats off for you    …..With Regards, DUMBO D' GREAT  "

 

WScript.Sleep 400

 

WshShell.SendKeys "%{s}"

 

2.      Enter the recipient name in place of “abcd@abcd.xyz“ and enter the content which you want.

3.      Now save this notepad with any name having extension .vbs.

4.      Double click the vbs file you will see automation in your outlook.

 

Enjoy by fooling your friends (especially Non-Technical).