SQL Server

< <

SQL Server Helper - Frequently Asked Questions - SQL Server 2005 - VARCHAR(MAX), NVARCHAR(MAX), VARBINARY(MAX)

http://help.outlook.com/en-us/140/ms130896(v=SQL.90).aspx

Using Large Value Types

In previous versions of SQL Server, working with large value data types required special handling. Large value data types are those that exceed the maximum row size of 8 KB. SQL Server 2005 introduces a max specifier for varchar , nvarchar and varbinary data types to allow storage of values as large as 2^31 -1 bytes. Table columns and Transact-SQL variables may specify varchar(max) , nvarchar(max) or varbinary(max) data types. Previously, only SQL Server data types such as text , ntext and image could attain such lengths.

Compiled » Why is SQL Server So Slow?

I’ve been asked this question a few times when looking into performance problems on a website, and the short answer is, it’s not. SQL Server is a very efficient database. It’s important to remember that a database is just a runtime for your SQL code. It’s just doing what you ask it to do, nothing more, nothing less.

http://blog.stevex.net/why-is-sql-server-so-slow/

By Bill Graziano on 15 May 2006 | 2 Comments | Tags: Performance Monitors , Profiler & Trace sqlec writes " I am attempting to analyze a stored procedure that I have written and have a question regarding profiler, What exactly are reads?

Examining SQL Server Trace Files

Troubleshooting Performance Problems in SQL Server 2005

Published: October 1, 2005 Writers: Sunil Agarwal, Boris Baryshnikov, Tom Davidson, Keith Elmore, Denzil Ribeiro, Juergen Thomas Applies To: SQL Server 2005 Summary: It is not uncommon to experience the occasional slow down of a SQL Server database.

http://technet.microsoft.com/en-us/library/cc966540.aspx

http://vyaskn.tripod.com/analyzing_profiler_output.htm

NEW!!! Subscribe to my newsletter: How to identify SQL Server performance issues, by analyzing Profiler output? (See also: Automating server side tracing in SQL Server ) It is always better to be proactive than reactive, when it comes to identifying and eliminating SQL Server performance issues. In this article, I am going to explain the method I follow, to identify performance issues in my database applications, before those applications go into production environment. Once the application is completely built and tested, I will conduct something called a "Load test" or "Stress test".

Identifying performance issues using SQL Server Profiler

SQL Server Optimizing SQL Server CPU Performance Zach Nichter

SQL Server: Optimizing SQL Server CPU Performance

http://technet.microsoft.com/en-us/magazine/2007.10.sqlcpu.aspx

SQL Server Native Client: Connection strings and OLE DB - Microsoft SQLNCli team blog

http://blogs.msdn.com/b/sqlnativeclient/archive/2009/05/07/sql-server-native-client-connection-strings-and-ole-db.aspx

(Anton Klimov, a developer on the SQL Server Native Client team, wrote the following article.) Connection strings for an OLE DB provider is a concept that causes a lot of confusion. One problem is that OLE DB itself does not define connection string as a provider concept. The documentation at Connection String Syntax ( http://msdn.microsoft.com/en-us/library/ms722656(VS.85).aspx ) says: "A connection string is a string version of the initialization properties needed to connect to a data store and enables you to easily store connection information within your application or to pass it between applications.

http://www.packtpub.com/article/moving-a-database-from-sql-server-2005-to-sql-server-2008-in-three-steps

Moving a Database from SQL Server 2005 to SQL Server 2008 in Three Steps | Packt Publishing Technical & IT Book Store

Share this page via Facebook, Twitter or LinkedIn. Your message has been sent. How would you like to send this article: Save this article to your account for easy access.

Install

http://msdn.microsoft.com/en-us/library/aa226054(v=sql.80).aspx

CAST and CONVERT

Explicitly converts an expression of one data type to another. CAST and CONVERT provide similar functionality. Syntax

Journey to SQL Authority with Pinal Dave

Denny Cherry, Contributor As with other applications, SQL Server applications need memory to run. However, unlike most applications, SQL Server allows you to decide just how much memory it can use. That's good because SQL Server likes lots of memory. Server memory options are set either within the GUI or with the sp_configure procedure by adjusting the "max server memory (MB)" setting. Setting server memory properties.