This would be that SP with the information put in based on what I gave.

CREATE Procedure spHugeTable_IncrementalUpdate( @RowsPerBatch int )

AS

UPDATE

GHOSTDATA

TOP

(@RowsPerBatch)

SET

Regjimi = 'MI88'

WHERE

LEFT(NR_KEK,2) IN ('08','07','06') AND

Regjimi != 'MI88'

GO

So then...

Do you have an existing table you are importing to?

If so it sounds like one of the columns is too short

Ex. Source length is 10 desitnation length is 5.

For the...

It all depends on several factors but 30 minutes may be the best you can do.

On thing to keep in mind is how the change is handled in the...

Ian Yates (2/17/2008)

---

And I would get your reporting tool to do the cross-tab rather than trying to bend a SQL resultset to do it. For example, both Crystal Reports...

I have to say Biometric data used as proof of who you are is the one that scares me the most. As has been proven time and time again encryption...

I agree don't convert to varchar, try instead using DATEADD w DATEDIFF to alter the date itself. Here I made that tweak along with a tweak of get the MAX(run_date)...

All depends on how you want to manage. Sounds like the view may do what you want but could be a stored procedure or your pplication could handle limiting the...

SQL does not automatically rebuild indexes are large deletes it just leaves the spaces marked as deleted (the data is actually still in the database until it is overwritten). Check...

declare @x sysname

set @x = 'my_mother_told_me '

select datalength(@x), len(@x), right(@x,len(@X))

Actually that is easy. You stated the following...

You should not see an issue on collection side (as long as the collection side is on another server). You might thou in reporting and that is what you have...

The real question here is what is your goal. You are using Right but the net affect is the same as using LTRIM

LTRIM(ColName),

With LEN it does not count trailing blanks.

From...

OK then what I have done when I want no interferance and there is no real time need is this.

I have 2 tables in my capture database

CaptureTable1

CaptureTable2

I chose to use...

Depends. What is you actual goal for the data? I have used several different methods including two input tables with a single SP that flips nightly so I can move...

The second is what MS demonstrates and would be what I use if I have to.

My only concern is the first if something goes wrong with the test for condition...

What is the exact error message?