I like the solution Gail handed over.

Especially because it lets you identify the bogus information easily using "WHERE HardwareNumber is NULL".

So, unless you really need this column to be...

You're encountering one of the "little" mishaps known with msaccess db.

did you try something like this ?

Declare @mycounter int = 999999900

UPDATE tblAsset

SET HardwareNumber = @mycounter

, @mycounter +=...

Kick out ALL udfs you use and write the proper query to fetch the data you aim for.

Without a sqlplan, it is up to our imagination to figure out...

:blush: regarding HP, I can only tell you should upgrade practically all drivers before throwing it into production.

We learned that the hard way when we were forced to move...

Until now, the obvious question has not been raised :

Is your SQLInstance on the latest service pack ? How to obtain ...

Select Serverproperty('ProductVersion') as ProductVersion

...

vinu512 (6/14/2012)

---

I am really sorry guyz.....I forgot to mention that our server is SQL Server 2005.

I am really sorry to have posted in the wrong Section.

Johan, your solution of CDC...

- it's all in your db log, but it may take some effort to get it out ... or a vendor tool.

- Is this a one time operation or is...

Did you try using it with level indication ?

;

with cte ( EventID, EventType, EventName, ParentEventType, ParentEventName )

...

-

Nice article, Robert. 😎

Nice enhancement of the GUI. I didn't pay much attention to it, because I assemble my scripts using a script generation script 😉

here are some other refs ( Gail showed you _the_ one 😉 )

- see topic "Restoring a Filegroup From a Full Backup" at http://sqlserverpedia.com/wiki/Restoring_File/Filegroup_Backups

- Of course there is always Books...

I would start making the current log-backup of that database !

Then it should be able to get you to the current state, starting from your previous full backup.

If you can,...

1) there is no column store index with SQL2005 !

2) SQL2012 column store indexes turn your table in read-only mode !

Did you try to find the issue in the data using the isdate function ?

select Datecol, ISDATE(Datecol)

from yourtable

where ISDATE(Datecol) = 0

I see in your example triggers all on table_1, you're only updating table table_2 in the first one.

For that one, I would use

...UPDATE cs

...