That is because we append our transaction log backups to the same file each day.  It makes sense that if each of your transaction log backups are written to seperate...

Your best bet at this time would be to look at your data and query and see how you can break it down into smaller batches rather than updating all...

You have it at the end of your procedure, it just isn't coded right.

You have:

--if (@ogt_code = 'Golf Course' and @ret_value >1) --I added this to try to fix

    --select...

Shouldn't the select in the if statement look like this:

select @ret_value = @ret_vale + 1

I would prefer to use a set statement where you are using select to set @ret_value:

set...

If you are looking at dynamic sql and accessing variable, look at using the extend stored procedure sp_executesql.  You can find information about that procedure in BOL and I believe...

Here is how I do it for one of our databases:

RESTORE DATABASE [H88TRN]  -- Restore of full backup

FROM  DISK = N'F:\sql_backups\H88PRD\H88PRD_20060804.bak'

WITH  FILE = 1,

      MOVE N'H88PRD_data' TO N'F:\sql_DBs\User_DBs\H88TRN\H88TRN_Data.mdf',

      MOVE N'H88PRD_log' ...

I have a default instance of SQL 2000 and a named instance of SQL 2005 on my box as well.  I have no problem selecting the named instance of SQL...

Another way:

select * into TableB from TableA where 1 = 2

Be sure TableB does not exist.  Also this will not copy indexes, constraints, etc.

If it is running 6 minutes, you may still want to do some more work.  I would suggest looking at your current indexes and perhaps running SQL Profiler to see...

Actually, I've used this to do some Test-Driven Development in SQL Server.  It has all been manual at this time, but it's let me capture updates without destroying the underlying...

I stand corrected on stax68's code.  My misperception was on where the criteria select was being completed.  I have done some testing and I am posting those results here for...

After wrestling with it some more, I have come up with a viable solution using a derived table and

a cross join.  Please take a close look at the query to...

I have made some updates to my test code:

set nocount on

create table dbo.SchoolAttendance(

    AttendanceRuID int,

    StudentID int,

    AttendanceDate datetime,

    AttendanceTyID int,

    RollupCount int,

    termID int null

)

create table dbo.SchoolAttendanceTy (

    AttendanceTyID...

Actually, not.  In your code, you have hardcoded the student id.

your code:

select sat.AttendanceTyID

, sat.Description

, sar.AttendanceRuID

, 169 StudentID

, sar.AttendanceDate

, isnull(sar.RollupCount,0) RollupCount

from SchoolAttendanceTy sat

left join...

Here is an update of what I have done:

set nocount on

create table dbo.SchoolAttendance(

    AttendanceRuID int,

    StudentID int,

    AttendanceDate datetime,

    AttendanceTyID int,

    RollupCount int,

    termID int null

)

create table dbo.SchoolAttendanceTy (

    AttendanceTyID...