I am still perplexed by this one. For clarity, here's a rundown of the situation.

This select against the staging table returns one row.

select * from WorkDB.dbo.ContractItems_Staging cc ...

By "client" I did mean client app, so I was saying the same thing about SSMS. Why do you need 16 million plus rows to appear on your client?...

Sounds like a client issue -- like your client doesn't have enough memory to handle the result set that is returned from the server.

Something like this executed against that DB:

select * from sys.database_permissions d inner join sys.database_principals p

on grantee_principal_id = principal_id

inner join sys.objects o on major_id = object_id

order by p.name, o.name

Ah, yes, the old Jet issue. Not only did I have to use SSIS, I had to run it at the command prompt using the 32 bit version of...

david_wendelken (8/25/2010)

---

jeff.mason (8/25/2010)

---

Only major issue we've seen is SharePoint -- Polyserve...

Is is SO much easier to support than MS clustering. ...

And yes, you can Active/Active as you describe with multiple nodes on one cluster unit. Just be sure to scope out the hardware/configure SQL settings so you can function...

Perry Whittle (8/24/2010)

---

partitioning, transparent data encryption, data\backup compression, indexed views,online restores, .......etc

Depends on features you are going to need. Chances are if you have managed with 2005 Std so far...

If you are willing to spend some serious money, you can buy a log reader that can do what you are asking for -- but you need a knowledgable DBA...

Our company's concept of "cloud" is that you have a large set of servers clustered by Polyserve that have many instances of SQL, and when an app needs a database,...

Do you have a link to the article so we can put the statement into context?

Depends upon the size of the DB and how critical the recovery of data loss is. For small to medium systems, my rule of thumb is nightly full and...

Hate to sound snarky, but yeah, the better way of dealing with it is to license per processor if you are using a web app. Best practices specifically recommend...

KILL should only be done manually by a trained DBA on a production environment. Period. A user app should NOT be able to kill processes. Too unpredictable...