I tried your example and modified the constraint into Allow Null values and insert the rows and it did converted into default value.

but the problem is I cannot modify...

In the first statement, you are inserting value that is why it's not failing.

I think the default means that if there is null value than store whatever value in...

Here is the insert statement

INSERT INTO TRANSAC_ARCHIVE

SELECT top 1 * FROM TEMP_TRANSAC where post_pd is null

Here is the table definition.

CREATE TABLE [dbo].[TRANSAC_ARCHIVE](

[GROUP_ZZ] [int] NOT NULL,

[PATIENT] [numeric](12, 0) NOT NULL,

[INVOICE]...

Looks like it is a default constraint issue. There is a default constraint in the table and when it's try to insert null values it throw following error. There...

I just found that there is a null value in the partion filed which is giving a problem. I already have default constraint on the parttioned field that if it...

we have data warehouse environment here and millions of rows gets inserted into the tables every night. If I use FK constraints then do you think it will affect the...

Thanks guys,

Looks like there is only way which ALZDBA has mentioned by creating FK constraints.

I googled a lot but did not find anything new. Can we create a trigger on...

Thanks guys, Great help. I modified like this. Just for testing purpose, i am trying to drop TT and TT! tables and getting the error. which is good.

ALTER trigger [TR_CaptureEvents]

on...

I have fixed the issue. Actually, it was coding problem in the stored procedure not the db-reindex issue I know the server is not big enough to hold this huge...

SERVER Configuration : VM, 1 CPU, 1600 GH speed and 4 GB RAM

using following command.

ALTER INDEX ALL ON DBO.TABLENAME

...

Actually, this is the stored procedure I ran every night and stored in the Missing_Indexes table. In the table , I check the column called Overall_Impact, if the this is...

Thanks guys,

I have modified the query little bit. Instead of using view in the query , I am using the table directly. somehow when I use view, query optimizer...

This query returns only 23 rows. I cannot use covering indexes because of SQL 2000 server and it does not support convering indexes.

There is a clustered index on following fields and group_zz is the part of the primary key indexes.

[GROUP_ZZ] ASC,

[PATIENT] ASC,

[INVOICE] ASC,

[TRANSACTION_ZZ] ASC

) ON [PRIMARY]

I also checked the fragmentation.

DBCC SHOWCONTIG scanning...

My Tempdb is on a separate drive called I drive. I have separated tempdb into two files on two different drives I and G and both the drives have enough...