Correcting database GUID default value corruption.

NETKEEPER^{^{^�}}
nklin1.gif (3727 bytes)
|Home|Products|Demos|Tech Support|Top FAQ list| Help Desk Software| CRM Software|

Correcting database GUID default value corruption.
Document ID : 000-000755 Created: 4/23/2002 Last changed on: 4/23/2002

Most likely one or more tables in the database have been damaged in some way. Sometimes, this is not an easy item to correct.

Solving this kind of problem requires SQL DBA knowledge.

When SQL returns an error such as "can't insert a null" or similar constraint violation you need to look at the attributes of your working database so you can find where was the database configuration changed or damaged.

In this case SQL Server is saying "I can't insert a new value because the value of GUID is null and that is not acceptable".

The next thing to do is to backup your database (so you can go back) and open Enterprise Manager. Then locate the JTSNK table and manually add a new row. If you get the same error, then you have located the source, but not the cause, of the problem. At this time also check that there are no "blank" (empty) rows. Delete the empty rows if they exist, these are probably malformed entries due to the current problem. Make sure to backup the database before deleting anything.

Next Open the table "for design" and check that the GUID column has a default value of "newid()". If the value is missing, then you need to add this default. (see the same column in other tables for the exact syntax)

Alternatively, try re-run the guidtrig.sql that creates all such defaults.

This solution text WEB page is automatically generated from your knowledge base and service data by NetKeeper Help Desk Software or NetKeeper CRM software. You can customize the pages to your site's look and feel or even include advertisements.