Database

Rob Graham wrote:

150 column table doesn't sound like a good design...

Tim Carmichael wrote:

I still have to delete approximately 3/4 of the data.

Tim Carmichael wrote:

, over the weekend, the database added another extent (20%). There is concern that the deletion process is causing the database to grow.

Rob Graham wrote:

Wouldn't it make more sense to copy the 25% you want to keep to a new database, then drop the old database?

Tim Carmichael wrote:

s is a 24/7 production environment and I cannot recreate and move the data.

Rob Graham wrote:

But you can afford to let the database grow by 20% increments?

Rob Graham wrote:

It is better to run big dbs like this at a fixed size (no growth), and run a free space monitor / purge routine on a regular bas

Dayekh wrote:

I want to STORE the TimeEstimate FROM the Request table INTO the QuoteRequest Table WHENEVER the AddQUOTE Stored Procedure is executed. This will effectively be populating the QuoteRequest Table with records of all the Requests which have been Quoted, and hence will allow me to display this info in a datagrid.

I don't know how to go about doing that.

Colin Angus Mackay wrote:

When you run the stored procedure, does it not already populate QuoteRequest rows?

QuoteRequestID<br />
RequestID<br />
QuoteID<br />
NoOfQuoteDays

Dayekh wrote:

I can do insert/update/delete SPs, but in this instance, I think I will need an insert SP within an insert SP if you see my meaning.

CREATE PROCEDURE dbo.MyStoredProc
@a int,
@b int,
@c int,
@d int,
@e int,
@f int,
@g int,
AS
    -- Do and insert
    INSERT MyTable(a,b,c) VALUES (@a, @b, @c);
 
    -- Do an update
    UPDATE MyOtherTable
        SET d = @d, e = @e, f = @f
        WHERE g = @g;
GO

CREATE TRIGGER MyTrigger ON dbo.vwMyView<br />
INSTEAD OF INSERT AS<br />
<br />
SET NOCOUNT ON<br />
<br />
DECLARE @MyVal NVARCHAR(50)<br />
<br />
SELECT @MyVAL = MyVal FROM INSERTED<br />
<br />
IF @MyVAL IS NOT NULL<br />
BEGIN<br />
INSERT INTO MyTable VALUES (MyVAL) FROM INSERTED<br />
END