Just bear in mind that there is a subtle difference in behaviour between the coalesce method and the Varible IS NULL OR Variable = Column method. Specifically when the...

That's no a serious problem.

As the output from CheckDB said:

Why not?

It's included in all editions of SQL 2005, from enterprise right...

There's your culprit. Index rebuilds are fully logged and have nasty effects on a tran log.

You can...

CheckDB, when run without options, just checks for errors.

The best options for checkdb (when run as a regular integrity check) is with the ALL_ERRORMSGS and NO_INFOMSGS options.

If you get corruption,...

Are you sure your windows login is a member of the sysadmin group?

Please post in the appropriate forum.

In my opinion, the 'repair minor errors' option should not be checked. Minor corruptions may indicate larger problems in the future. If they get repaired...

All of the DMVs are present in all editions of SQL 2005.

What error are you getting?

Ow! Multi-statement table-valued functions are an absolute pain and they tend to perform very badly with larger rowsets.

How many rows do those return?

This update is not necessary. You should be...

SQL won't release memory by itself. That's by designs and it's expected behaviour. It will only release memory when the OS requests it (in cases of low memory) or when...

What you can do is just check the size of your log backups. That'll give you an easy way to get the average log volume.

That may not be possible. You're doing a lot of work in there.

What are these?

dbo.fn_ProfileLegalVechile(@ProfCode,@Branch)

dbo.fn_ProfileWareHouse(@ProfCode,@WHCode)

dbo.fn_ProfileCurrency(@ProfCode,@CCYCode)

The suggestions aren't mutually exclusive.

You could try DBCC SQLPERF(LOGSPACE) for the percentage of the file used. You could also count the rows in fn_dblog(null, null), but that can get intensive and time consuming,...

Same syntax as for a regular...