Wow, SELECT CONVERT(VARCHAR(25), GETDATE(), 22) is soooo close. And undocumented.

Reason for this is, we export the data to an Excel spreadsheet, which is converted by our customer to another version...

If the apps really are not related, I can't see any reason not to have separate databases.

Setting up maintenance plans / log-shipping / etc... are one-time costs.

What happens if you...

What is the error message?

What jmcgarvey 9/19/2012 7:28 PM said: Truth!

Been DB-Analyst/Architect/Admin/Developer for 15 years and, given the choice, would not change a thing.

Progress!

Authentication Type: Negotiate

Protocol: Kerberos

Authenticated identity: Domain\Me

Thread identity: Domain\Me

Windows identity: Domain\SQL-Service

Environment identity: SQL-Service

We're now using Kerberos at least as far as the IIS Server!

So now we just need to get to...

Your way did work with a single entry in $Remove. When I added a second entry, neither was removed??

Weird.

I was also curious as to why you used a for ......

Thanks again Bruce.

I got it working using a foreach $Result (If not in $Remove, add to $FinalResult) approach.

Works reasonably fast. (13K $Results to check against a list of 500...

I tried your code, it gives me an error:

An error occurred while enumerating through a collection: Collection was modified

; enumeration operation may not execute..

At ps1:10 char:8

+ foreach <<<< ($result...

SORRY: This should have been a new topic, reposting.

Hi,

I have 2 Array or ArrayList objects, with data like

$Results = New-Object system.Collections.ArrayList

$Results.Add("IMP_Trn_Project_Agent_6,User1")

$Results.Add("IMP_Trn_Project_Agent_6,User2")

$Results.Add("IMP_Trn_Project_Agent_6,User3")

$Remove = New-Object system.Collections.ArrayList

$Remove.Add("User2")

How can I efficiently remove from the...

That does get them, but also returns the PK, which in my case I want to ignore.

I was hoping there was some property or combination of properties in SMO.... And...

I was able to Set-Content of the source files to Unicode, and they appeared OK when opened in SSMS.

I had a test version working fine; but when those files were...

Forgive me, maybe it's too early on Monday, but I'm not sure how that helps me?

The source file is fine, it's getting the accents into SQL Server that's problematic.

Add a column named IgnoreThisRow, and set it to true for empty rows, false for real rows.

Interesting: the prod (and problematic) SQL box is bound to what is, according to our network admin, the PDC for AD; I was forcing AD replication from it to the...

I should have mentioned again that our users are in AD groups, and it's the groups that have logins.

And again, not all members within the same group experienced difficulties, only...