Top ten issues in SQL Server database development

Developing in SQL Server allows you to Xiande and find quick solutions. We edited the top 10 common questions about SQL Server development. The common name constraints on tables and fields are explored. Learn how to troubleshoot concurrency problems and write stored procedures without understanding T-SQL. See the quick reference for these solutions and learn more.

The 10 questions you might ask in SQL Server development questions:

1, what is the common name of the table and field constraints?

2. Is it possible to write stored procedures without understanding T-SQL?

3. How do you compare the performance of CLR stored procedures and functions in T-SQL?

4. How can I use another stored procedure to produce results in one stored procedure?

5. How do I troubleshoot SQL Server 2005 concurrency issues?

6. What tools are used in SQL Server 2005 to replace the Query Analyzer?

7. Can you provide some detailed information about SQL and T-SQL?

8. Is there a new index type for SQL Server 2005?

9. How do I create a script to make a selection in a table?

10. How do I list the database tables that have no records?

Common name constraints for tables and fields

Expert answers:

Table and field names under SQL Server 2000 have a limit of 1 to 128 bytes and follow the rules used for identification.

The first letter must be one of the following:

· The letter specified in Unicode Standard 2.0.

Unicode definitions of letters include: Latin alphabet, from A to Z, except for letters from other languages.

· Underscore (_), at sign (@), or number sign (#)

The beginning of these symbols as identifiers in SQL Server has a special meaning. An identifier that begins with an at sign (@) represents a local variable or parameter. An identifier that begins with a number sign (#) represents a temporary table or procedure. An identifier that begins with a two digit sign (# #) identifies a global temporary object.

The names of some Transact-SQL functions begin with two at symbols (@@). To avoid confusion with these functions, it is recommended that you do not use identifiers that begin with two at symbols (@@).