The title is SSIS error on access import.

The last answer has currently 3 votes and starts with There is import wizard bug, when you select 'copy data from one or...

Perhaps an import wizard bug

See section "the automatic generated sql have single quote on table name, which cause error message"

I don't have a Core installation to test with. But you can modify the registry from the commandline with reg[/url]

32-bit versus 64-bit browser?

Some things only work in 32-bit IE

Promising. I'll have a look at it.

Could it be that there is a size limit?

Funny cartoon

That means you don't filter the value of ID1

and only filter on ID2,3,4,5,6

Something like

where (@IgnoreID1='Y' or @ID1 in (......))

and (@IgnoreID2='Y' or @ID2 in (......))

...

ID1 value X

ID2 value Y

ID3 value Z

ID4 value A

ID5 value B

ID6 value C

Ignore ID1: N

Ignore ID2: N

Ignore ID3: N

Ignore ID4: N

Ignore ID5: Y (do not filter on B (the value...

Add extra parameters with Ignore IDX with "No"/"Yes" (with default No) and adjust the dataset for it?

Enjoy your retirement George

I can't speak about if it is good practice or not. Is is more a division of roles practice (We manage the infrastructure, you manage the users)

As long the Active...

You can have users from another domain as long the server domain trusts the user domain.

Brandie, also got the Stairway to U-SQL twice today

Great article

Could you change the where-clauses to use proper date-variables instead of strings

WHERE CalendarDate BETWEEN convert(date,'2/27/2016',101) and convert(date,'3/1/2016',101)

instead of

WHERE CalendarDate BETWEEN '2/27/2016' and '3/1/2016'

If you can't join them in the database, you can use the Lookup function.