I've no idea. Frankly I would be amazed if it were true.

The only possible benefit that springs to mind is if you use the table hint NOLOCK then you...

Almost any commonly used expletive will do as a name of SMSS.

You have quite a mix of terms above.

Query Analyser is SQL 2000 and below but you mention SQL2005?

If you are using SQL 2000 try using an IMAGE or VARBINARY fields...

If you write crap code in PHP/MySQL then it is just a susceptible to hacking as for anything else.

Although PHP is popular the number of PHP programmers is dwarfed by...

When I worked for a company supplying solutions the attitude was altering the source code violated any support contracts.

It was a business issue not a technical issue

If you keep your stored procedures as scripts then you can use SQLCMD to run those scripts and pass in a variable to append to the CREATE PROC statement.

That variable...

I suspect that your condition

ltrim(rtrim(E.acc_typ))+'/'+rtrim(ltrim(E.acc_no)) = ltrim(rtrim(D.autopay_acid))

could be modified.

If the application that writes into autopay_acid LTRIMed and RTRIMed the data then the query may be able to use any indices...

SELECT
   YT.Cash_Locale ,
   YT.Cash_WTD ,
   YT.Cash_PTD ,
   YT.Cash_Daily ,
   DT.MaxCashWTD ,
   DT.MinCashWTD ,

 ...etc

FROM dbo.YourTable AS YT, (
...

I am not a SAN expert but my understanding is that it depends how your SAN is organised.

My understanding is that RAID5 is slow for writing (because of its striping...

DECLARE @NextAccount INT
SET @NextAccount=0

WHILE @NextAccount IS NOT NULL
    BEGIN
        SELECT @NextAccount=MIN(acct)
        FROM dbo.YourTable
...

Save yourself months of work and buy Apex SQLDoc or Innovasys DocumentX.

I spent 4 months documenting a huge database and then found out that DocumentX could do it in under...

CAST(YourField AS YourDataType)

YourDataType could be REAL, FLOAT, DECIMAL etc.

So the client wants a system that gains an extra 5,000 pages per week and at present has 1.5 million pages of records which they insist that they will page...

I think the point with "never look onto tables directly" is that if you give read access to the table then someone can decide what they want to read from...

It sounds as if SQL Server is escalating the locks from ROWLOCK to PAGELOCK.