Humour me 😀 Set the log to 100MB and see what happens. Best practice is for tempdb to be big enough without growing anyway.

The reason for the error...

SQL Server will attempt to grow the log by 10% and report this error if that is not enough; it won't try another 10% within the same transaction.

Your best bet...

The only other thing I can see is that you have left out the space in Initial Catalog in the connection string.

What schema is the table in? If it's not dbo, or the default schema of the user is not dbo, you will have to explicitly include it in your...

Not quite what you're asking, but Brent Ozar has blogged about how to analyze the perfmon data in Excel.

http://www.brentozar.com/archive/2006/12/dba-101-using-perfmon-for-sql-performance-tuning

I have a script that gets most of what you want, together with a few other bits of info.

It's a bit messy as it has evolved over time, so you...

When you created the new file in the new filegroup you set a very small initial size with small growth increment.

To avoid excess fragmentation, you should set the initial size...

Taking the basic idea posted by Chris Morris (page 2 of this thread) and modifying the string build part gets the following. If there are duplicate properties for a...

There are a few tips here. It refers to SQL 2000, but the principles are the same.

http://msdn.microsoft.com/en-us/library/aa178096.aspx

In my experience, setting ROWS_PER_BATCH and using BULK LOGGED recovery model have been...

You can do this with a tally table (see the excellent article by Jeff Moden for more detail).

Create the tally table, if you don't already have one:

select top 10000 identity(int,...

Is this what you want?

insert into emp (lastname, firstname, initials, [role], [status])

select LEFT([name] , CHARINDEX( ' ', [name],1 )-2),

RIGHT( name , CHARINDEX(' ',reverse(name),1)-1),

Initials, 1, 1

from #emp as r

I'm not sure...

I've just tried this on SQL Server 2005 Standard

select 'x' where 1=0 and 1/0=0

select 'x' where 1/0=0 and 1=0

select 'x' where 1=1 and 1/0=0

select 'x' where 1/0=0 and 1=1

The...

Before running DBCC CHECKDB, run DBCC UPDATEUSAGE.

This is because SQL Server 2000 can have some incorrect counts, which results in warning messages being produced by 2005 in CHECKDB.

I have written a brief description of this exact problem here:

OR Condition Performance

I have lost count of the number of times I've seen this, and at first sight it looks...

You could also look at master..sysperfinfo

This allows you to retrieve the value of some performance counters programmatically.