crazy4sql (3/22/2011)

---

if your database have enough free space then it will not affect performance.

But if your database almost full and then you increasing the space then you will see more...

It must have to do with how SQL Server handles data-type conversions internally. The rule surrounding converting character data to the NUMERIC/DECIMAL data type requires that there be either a...

Kindly provide the DDL and DML used to construct the environment in your example.

You can vote for an enhancement to add support for that:

http://connect.microsoft.com/SQLServer/feedback/details/339410/please-fix-the-string-or-binary-data-would-be-truncated-message-to-give-the-column-name

PIVOTs and cross-tabs change rows to columns. What you want is UNPIVOT, i.e. to change columns to rows.

http://msdn.microsoft.com/en-us/library/ms177410.aspx

You have it good...

I wished many times that...

It's also known as the "double-hop issue" (winces, grits teeth)

The Agent tables are not my favorite thing in the world to dig through 😀 The way dates are stored, the lack of an easy way to find a job's...

Glad to help...now please use it to post some DML so we can help you with your solution 😉

Actually used in production:

- proc: access web services

- proc: accessing third-party address standardization software

- scalar function: use assemblies installed in local GAC containing proprietary encryption methods

- data type: IP address

Toying...

Please proceed knowing that this is not an SSMS / Query Analyzer issue.

Hopefully you will find the issue by checking these four things:

1. In DEV: Is there a table name...

What you'll want to do is to make the last step of the job look at the result of the previous steps and then either raise an error to fail...

Third-party drivers used via Linked Servers are a notorious source of memory leaks. Depending on how your app maintains its connections, the use of the procedure sys.sp_xml_preparedocument to prepare an...

I have not used it however a SQL Skills blog came to mind...here is a good primer backed up with some real-world experience (see comments from readers too): http://www.sqlskills.com/BLOGS/KIMBERLY/post/SQL-Server-2005-and-2008-Compression.aspx

6GB would be a fine place to start...max memory is an art not a science. Glenn has 6400MB recommended on a system with 8GB of RAM which is a shade...