Old post I know, but bumping this just to give my thanks - setting the user and password in the linked server on SQL Server did the trick for me....

When you're asking questions about specific SQL queries, it's generally good form to post the table creation and population queries to save us the time of having to do that...

Ahh okay, I think I understand what you mean. If I'm reading you right, we're essentially talking about columns which are not part of an index, but are still used...

Now I'm even more confused. Earlier in this thread, Grant suggested updating the statistics after an index rebuild was not the right approach, since the statistics are already updated by...

if you don't mind me asking, I really do wonder, what possible reason could you have for wanting to recode your numbers as letters o_O? Some sort of archaic way...

So just to clarify, since I've personally never ran an update of statistics on any of the databases I've administered, proper maintenance is, for each table in a database, to...

My personal preference for queries which return recordsets is:

usp_Get[TableName]_By[ColumnList]

EX:

usp_GetStudent_ByLastName

For queries which perform INSERT/UPDATE/DELETE:

usp_UpdateStudent

The INSERT/UPDATE/DELETE are all performed in one single query, generally through an upsert or MERGE statement.

As far as I know, there's two main reasons to set NOCOUNT to ON:

1) The rowcount for each individual query in a stored procedure is rarely relevant, so small amounts...

I'm aware of the limitations of wildcards on indexes, which is one of my principal concerns of performance - normally, a table with several hundred thousand rows marked as "deleted"...

The idea of multiple schemas to me doesn't really solve the problem - it's still going to involve long tables, just that particular clients might only be viewing part of...

Fair point - I'll make sure that the UPDATE parts do, at very least, index scans, if not index seeks

Perhaps I should have given a bit more insight - the input for the stored procedure is a TVP because the caller is a .NET application. Rather than sending the...

That's a valid point, though perhaps I should have mentioned that the product in question is a web-based portal. So for example if SQL Server Azure were to make some...

Regarding the security implications of using cookies for database access, I'm aware of them, and plan on dealing with that in due time.

As for the comments on propagating changes, thanks...