See https://www.imceda.com/support_knowledge.asp?action=resolution&knowledgeID=70 i.e. imcedas support pages which says: "This error has been fixed in versions post 3.1.0.5".

Oh my, only 8000 - we have 62 000 in the largest fax image db.

We have 4 databases with fax images (data type image) constantly being loaded from incoming fax messages. The largest db is now 9 GB, but so far we have no...

Example: 1 h 40 min with 215 GB of used data in the databases to 2 SAN-disks with SQL LiteSpeed resulting in 53 GB on disk.

The question was: "Each time you execute the following stored procedure, which updates the inventory table, it issues a deadlock error. What is the best way to fix the problem?"...

Aggree with Pitiyar and all you who say that changing HOLDLOCK to UPDLOCK would be the most appropriate measure.

I just contributed a script called "Add files to filegroups and log for many dbs" with I use when I add a new SAN-disk and want to expand database filegroups...

Great! I like the idea to use current msdb to create restore scripts on the spot. I suggest you include the possibility to handle several backup files for one database...