SQL Server and short tips – 1

• SQL Server is a backend system and its size limited by the Hard disk.
• SQL Server History:
• SQL 4.2 (oct 92).
• SQL 6.0 (jun 95).
• SQL 6.5(Apr 96).
• SQL 7.0(jan 99).
• SQL 2000(Aug 2000).
• SQL 2005(Nov 2005).
• SQL 2008(Aug 2008).
•  T-SQL is a Interpreted language and it’s not a full programming language.T-SQL comes from the SQL ANSI Standard language like PL,Postgre and MySQL.
• Sql Server 2005 express work only on 32 bit but Sql Server 2008 express work on 32/64 bit
• you can upgrade from SQL Server 2005/2008 Developer Edition to Enterprise edition
• You can run Sql 2005 or SQL 2008 side by side with earlier version but you need to consider the order of the installation and likewise you can use the Default instance name in different version.
• You can upgrade from SQL 2000(sp3) to SQL 2005 or 2008 but if you want to update earlier version before 2000 you have to upgrade it to SQL 2000 then to SQL 2005 or 2008.
• Database compatibility Level:
•  60 for SQL 6.0
• 65 for SQL 6.5
• 70 for SQL 7.0
• 80 for SQL 2000
• 90 for SQL 2005
• 100 for SQL 2008

So what is Database compatibility level?
Database compatibility represents the current version of Database which uses the specific version features or syntax that means for example some statements work fine with SQL Server 2000 and does not work with SQL 2005 so to run this statement in SQL Server 2005 keep the Database compatibility in 80 level.

You can change the database compatibility from SSMS or by using sp_dbcmptlevel system stored procedure.

• What about if I want to save my session with current Connections, Queries and other files so I can return back to it later on, so we can use a Solution in SSMS.

Let's see this example:

1. Open you SSMS and then go to File>New>Project and choose SQL Server Scripts
2. Open Solution Explorer and start your work so connect to the specific instance and run some queries even add some files as references and so on.