Pleasure.

I'm still unclear why you're using dynamic SQL at all. There doesn't seem to be a need.

See my edited post.

It is possible to do that as a check constraint, however be aware that email addresses are very complex to validate properly. See here for some details on what is...

You can't change sys.databases. It's a system view.

log_reuse_wait_desc tells you what the log is waiting for to be reused. Nothing more. It's a report of database information, not a...

It's always recommended to put TempDB on its own drive, especially if it's heavily used.

The recomendations to split TempDB into multiple files is usually to avoud contention on allocation pages,...

Try the yyyy/mm/dd date format.

set @fromdate = '2008/06/16'

set @todate = '2008/07/22'

Edit:

Oh, and this is also a problem

'set @date1 = ' + @fromdate + '; set @date2 =, ' + @todate...

Check that there's no automatic log backup job running and that the log hasn't been truncated between the full backup and the log backup you took.

The error 'too recent...' implies...

If you're in simple recovery mode the log automatically truncates at checkpoints. There's nothing you need to do.

The log file contains inside it a number of log segments. These store...

Compat mode 80 just means that the SQL 2005 features are not enabled. It does not mean that the database structure is still that of a SQL 2000 database.

Underneath...

Please run a checkDB on that database.

You actually don't need trace flag 3605. Just 1222 or 1204 is enough to write the deadlock info into the error log.

1204 puts the deadlock graph into the error log...

The statistics won't be there. They are not kept on table variables.

For this reason mainly, table variables are best used for small numbers of rows. I prefer < 100.

It's not...

Full backups do not truncate transaction logs. If you're in full or bulk logged recovery modes, only a log backup will truncate teh transaction log and make the space available.

Since...

It still doesn't have row statistics. Run the following with the execution plan enabled

DECLARE @testing TABLE (

id INT PRIMARY KEY,

somecolumn uniqueidentifier

)

INSERT INTO @testing

SELECT number, NEWID()

FROM...

Please don't cross post. It just wastes people's time and fragments replies.

No replies to this thread please. Direct replies to the following:

http://www.sqlservercentral.com/Forums/Topic515651-360-1.aspx