The more written the SQL script, the more often it feels that writing is too inefficient, regardless of the speed of the typing. When I personally write SQL scripts, I will at least arrange the SQL format to be easy to read, because others will read your SQL, whether in the program or in the script file, good typography not only makes people look pleasing, but also save time and effort when communicating with others. Don't ask team Member for a bunch of sql: Can you explain to me what a large section of SQL does?
Although Microsoft to SQL 2008 more than the version provides SQL Smart hints, but its response is too dull, and so on, we can already knock out a line of statements. And it does not provide the function of SQL code formatting, we can only do the manual format, the manual format of SQL will always take a lot of time.
System: Win7 x64 SP1 + SQL R2
The more written the SQL script, the more often it feels that writing is too inefficient, regardless of the speed of the typing. When I personally write SQL scripts, I will at least arrange the SQL format to be easy to read, because others will read your SQL, whether in the program or in the script file, good typography not only makes people look pleasing, but also save time and effort when communicating with others. Don't ask team Member for a bunch of sql: Can you explain to me what a large section of SQL does?
Although Microsoft to SQL 2008 more than the version provides SQL Smart hints, but its response is too dull, and so on, we can already knock out a line of statements. And it does not provide the function of SQL code formatting, we can only do the manual format, the manual format of SQL will always take a lot of time.
System: Win7 x64 SP1 + SQL R2
SQL Prompt 6.51. Download SQL Prompt 6.5, which is a compressed package with three files
Free sign-in points: http://download.csdn.net/detail/simadi/8916005
1) After the download is complete, unzip to get the following three items. One is registered tutorial doc, one is keygen keygen, one is the official original installation package V6.5.
2. Installing SQL Prompt 6.5
1) Run Sqlprompt_6.5.exe, all the way next until the installation is complete.
SQL prompt provides three features, and what we care about most is SQL Prmopt 6.5-Write, Edit and explore SQL effortlessly
2) Open SQL Server R2 on the toolbar, click SQL Prompt 5
3) Open the Sql.prompt.keygen.5.3.exe and copy the serial number to the window just now
4) Then click Activate, notice to break the network first, wait for a network error will be prompted, and then click Activate manually (offline registration)
5) Copy the code into the text box in the middle of the register to generate the corresponding code
6) Copy the generated code to the text box on the right and click Finish
7) Crack success!!
3. SQL prompt-assisted writing SQL in SQL Server
Note: SQL prompt also supports SQL Server 2005, and my own environment is SQL Server R2.
1) Smart Tips
The smart tips for SQL prompt are very sensitive, much better than the R2 comes with. When entering a keyword, even if you enter lowercase, it will automatically convert you to uppercase (in fact all SQL keyword capitalization is a more canonical way of writing), do not need to write the keyword and the normal word back and forth to switch the CAPS LOCK key.
In addition to the Code intelligence hints, it also provides smart hints for table definitions. Maybe you have a big table, but some fields you can't remember clearly, you don't have to go to Server Explorer on the left side of SQL Server to see the table structure.
2) SQL code formatting
Before formatting:
1 Create DATABASE Test 2 Go 3 use Test 4 go 5 6 CREATE TABLE Employees 7 (8 Id INT IDENTITY PRIMARY KEY, 9 Employeena Me NVARCHAR (+), EntryDate DATE11) GO14 CREATE TABLE Users16 (Id INT IDENTITY PRIMARY key,18 UserName Nvarc HAR (+), Gender CHAR (1), birhdate datetime,21 EmployeeId int22), GO24-SELECT u.username, e.employeename from Dbo. Users u27 INNER JOIN dbo. Employees e on e.id = U.employeeid
after formatting:
1 Create DATABASE Test 2 Go 3 use Test 4 go 5 6 CREATE TABLE Employees 7 (8 Id INT IDENTITY 9 PRIMARY KEY , EmployeeName NVARCHAR (+), entrydate DATE12), GO15 CREATE TABLE Users17 ( ID INT ID ENTITY19 PRIMARY KEY, UserName NVARCHAR (+), Gender CHAR (1), birhdate DATETIME, EmployeeId INT24 ) GO26 SELECT u.username, e.employeename30 from dbo. Users u31 INNER JOIN dbo. Employees e on e.id = U.employeeid
If you write a large segment of stored procedures or try, using SQL prompt formatting can save us a lot of time.
4. Using the soruce Control in SQL Server
SQL prompt provides a version controller of the database, and after I try to use this feature, I have to say that this is a really good feature.
The addition and alteration of tables, views, stored procedures, and functions in a database can be managed without having to fill out an Excel document record database change point every time the change is made.
The following pictures are a simple tutorial.
1) Click Link Database to Source control
It provides several interfaces connected to the source control, where I choose SVN as the database version controller.
2) Input SVN address and Development mode, development mode I chose multi-person sharing mode
The connected address and database are displayed when the connection is successful
3) Changing database operations
When I change the structure of the Users table, the users table will appear with a small blue icon indicating that the table has been changed and can do a commit operation.
There is a commit command in the table's right-click menu
Now to commit it, it will prompt you to change the table structure (I have added an address column to the Users table), click on the Commit button in the upper-right corner to submit
4) View History
I've made changes to the table before, and View history is a very important feature of versioning, now to verify that it works for the database.
Right-click->show history
There is a clear contrast between the front and back versions
5. Using SQL Prompt in Visual Studio
On the official website, it is clear that SQL prompt can only be used in database project or SQL Server project.
Using SQL Prompt with Visual Studio
SQL Prompt can integrated with Visual Studio 2005, and 2010. SQL Prompt only works in Database projects and SQL Server projects.
When we're doing a project, we can create a matching database project for our project to manage our tables, views, stored procedures, and other database scripts.
We are unable to use SQL prompt in general projects.
You can use it when we have created SQL Server project or database project, or a script file that opens the SQL suffix name directly in Visual Studio 2010.
The blog post http://www.cnblogs.com/keepfool/archive/2012/05/27/2519839.html about VS2010 not be able to use the SQL PROMPT5 problem in SQL The Prompt5.3.4.1 version has been repaired. Whether it is Windows7 x86 or x64 can be used perfectly!!!
Report:
SQL Server Development tool SQL Prompt 6.5 T-SQL IntelliSense Analyzer complete hack + Use tutorial