CREATE PROCEDURE dbo.SetNewPurchasePeriod

    @DateStart smalldatetime, @DateEnd smalldatetime, @price money

AS

DELETE FROM TABLE

WHERE ValidPurchaseDateStart BETWEEN @DateStart AND @DateEnd

AND ValidPurchaseDateEnd BETWEEN @DateStart AND @DateEnd

INSERT INTO TABLE (ValidPurchaseDateStart, ValidPurchasedateEnd,...

How do you assighn NULL?

Can you past INSERT statement you use?

Error must be there.

Jeff, you did not mention security concerns, when you need to give to all users full access to all tables, sometimes including system tables.

Than, you cannot limit the data scope...

Still does not make sense.

Create Function getData(@id uniqueidentifier)

returns @retResults TABLE (of_id uniqueidentifier, Value decimal(15,5))

AS

BEGIN

INSERT @retResults

(of_id, Value)

SELECT @id, fieldA

from table1

where tabel_id = @id

RETURN

END

I'm not sure why you need to pass original...

Create #Table with IDENTITY column, populate it with new data and than insert from #Table to destination table with Max(ROWID) + #Table.ID

You must do it in SP.

You should not allow application to run queries on tables or views.

SELECT IDENTITY(int, 1,1), <list of columns>

INTO #TempTable

FROM <your query>

SELECT * FROM #TempTable

So, Webproxy log - that's what must take all your attention.

I believe it carries all useless history staff in the worst possible way. I mean fully denormalised.

If you can delete...

Forget about SHRINKDATABASE for a minute.

You don't need much space on disk to perform big insert. Much non allocated space inside of mdf file will be quite enogh.

Find out which tables...

What about "fields from the rows that have changed"?

Trigger is universal thing, it will be fired everytime you do something to the data in your table. It not...

Which statement you are talking about?

Just make sure you've run  DBCC UPDATEUSAGE (0) prior to SP_SPACEUSED, otherwise results returned may be incorrect.

Use these:

DBCC UPDATEUSAGE

master.dbo.sp_MSforeachtable

master.dbo.sp_spaceused 'TableName'

Check out BOL for complete syntax and different options.

Thanks for "UP". Not really my area of expertise...