SQL Server MVP Hugo Kornelis has written a couple of blog posts about bin packing, see http://sqlblog.com/blogs/hugo_kornelis/archive/tags/Bin+Packing/default.aspx

If you want a fix table, the only option would be to import the lines as they are to crack them later. Or size the table for the maximum possible...

Maybe. All depending on the...

DesmoShane (7/30/2013)

---

You say that the view is created in tempdb and it can have a heavy impact ,so each time the view is accessed how is the view "rebuilt" does...

My biggest concern is the use of SELECT *. This is a bad thing to put in a view definition (or in application code in general).

Else, there is not...

Do you mean that the NOLOCK hint should be used? Have ye no...

No. Say that a procedure consists of four statements, A, B, C and D. Only statement C refers to the table X. Because statistics on X are updated, the plan...

For a crash-course in how to shred XML, you can read here: http://www.sommarskog.se/arrays-in-sql-2005.html#XML.

It's a little tricky to work with context_info. See here for how for examples: http://www.sommarskog.se/grantperm.html#context_info. (That's a section in a longer article, and you only need to read down to...

For a view, no. But for a scalar user-defined function WITH SCHEMABINDING can be important.

It could be the correct action to change the fillfactor to 70 or 80 for a specific table, if you have conducted careful analysis that your biggest problem is page...

From what you say, it does not seem that the collation matters, although collation mismatches certainly can cause performance issues. (But mostly they cause error messages.)

Ratherm I would think that...

decimal(10,0) and datetime are not really the same thing...

The error message is clear: it says that you need to add a computed and persisted column to the base table which...

AWE is definitely enabled.

Adding the startup option -g512 should not be a problem, and I recommend that you try that. This is a quite common thing to do.

When this problem...

The log you posted, disagrees with the output you posted from "SELECT @@version":

Microsoft SQL Server 2005 - 9.00.5069.00 (Intel X86) Aug 22 2012 16:01:52 Copyright (c) 1988-2005 Microsoft Corporation Standard...