This looks like a pretty good answer:

https://answers.laserfiche.com/questions/48435/SQL-Transaction-Log-is-taking-up-all-drive-space

Then read Gail's articles:

http://www.sqlservercentral.com/articles/64582/

http://www.sqlservercentral.com/articles/Transaction+Log/72488/

John,

Any chance you can upload a copy of your report? The fun part is that you have to provide some data for it. So you have two options:

1....

If you're using a matrix, you need at least one Row Group and one Column Group as well as one Aggregate...

So... this worked for me:

Row Groups: [PeriodEnd] (or the date...

Might sound like a dumb question, but what happens if you add a table to the report and drop the fields into a tablix but don't filter it. Just...

Okay, I was going to use a Calendar table to force the dates to exist. DAX is just still kind of mind-boggling.

I figured out the solution after the...

Not much for details. BOL (Books On Line... hiding under the F1 key) is your friend. Check out this article on CHARINDEX. It should get you started. ...

Here's the cool thing with DAX. You don't need a "proper" data warehouse. it works better if you have one, but it's not necessary. There are a...

If you have a copy of Office Professional Plus, then you can do a bunch of stuff with DAX and PowerPivot. Check out Kasper de Jonge and Rob Collie's...

and it takes a fair amount of time to learn... =) Not to be a wet blanket, but you get out what you put in.

I would imagine there is. Kind of depends on how good you are at SSIS, SSAS and sometimes SSRS. Ask Koen... he does it every day.

you're not joining to the Inserted or Deleted virtual tables, so your result set is not getting filtered. Once you do that, only the affected records will be updated.

Sounds like you tried to run an update query without a filter. You shouldn't need one. Something like this should work.

CREATE PROC uspInsertRecord

@ProductCode VARCHAR(10)

AS

BEGIN

INSERT INTO MyTable(ProductCode, SomeDateField)

VALUES (@ProductCode,GETDATE())

END

You need to return just the date portion of the datetime field. After that, it's easy.

You would have to filter the result set...

DECLARE @StartDateTime DATETIME,

@EndDateTime DATETIME;

SELECT top 100 Ltrim([text]),objectid,total_rows,total_logical_reads , execution_count

FROM sys.dm_exec_query_stats...

Alan,

Yup, I noticed that... The link I posted is to an article by Pinal Dave simulating LAG/LEAD in 2008. Otherwise, I would have posted a query.

I guess he could...