You are welcome. Don't get me wrong logon triggers are great. But understanding their limits is important.. They do a great job for tracking who and when...

Ok, you got me.. Stumped.. I'm absolutely sure it is something simple, something stupid.

CEWII

You might turn up the number of errors allowed.

CEWII

I agree, the flip is necessary. Sorry, it was late.

CEWII

What happens if you run it twice in a row? Does it die?

Also, is the datekey a date ONLY or a date/time. The field it is matching has...

How does date key...

Ok, that makes it a bit complex..

You'll have to pull the data needed from each source, make sure it is sorted, and make sure you set the source to indicate...

You might look at:

SSIS Package persistance locations

http://blog.techdreams.org/2006/12/ssis-packages-can-be-persisted-in-three.html

CEWII

Why don't you try:

[column1] =="1/1/1900" ? [column1] : NULL(DT_DBTIMESTAMP)

CEWII

I still see a couple issues..

1. You still need to handle DateKey

2. Does the table get cleaned before it gets filled? If so then add an exec SQL task...

Good method.

CEWII

First, the the EXEC SQL task can only take actions against a single server at a time. So you can't pull data from one connection and put it in...

bitbucket-25253 (2/24/2010)

---

My suggestion is ALL servers will met production security standards. Inform those connected with development/QA to suck it up, if not find another job. Harsh yes ......

Please see:

http://www.sqlservercentral.com/Forums/Topic872420-148-1.aspx

CEWII

If I understand your requirement, you have a server, we'll call A that receives the data. You have 3 other servers, we'll call C, D, and E that we...