Lynn Pettis (9/19/2012)

---

opc.three (9/19/2012)

---

Lynn Pettis (9/19/2012)

---

opc.three (9/19/2012)

---

Lynn Pettis (9/19/2012)

---

opc.three (9/4/2012)

---

Jeff Moden (9/4/2012)

---

opc.three (9/4/2012)

---

All sysadmins can execute any commands they wish and those commands will run in the context of the...

Lynn Pettis (9/19/2012)

---

opc.three (9/19/2012)

---

Lynn Pettis (9/19/2012)

---

opc.three (9/4/2012)

---

Jeff Moden (9/4/2012)

---

opc.three (9/4/2012)

---

All sysadmins can execute any commands they wish and those commands will run in the context of the SQL Server service...

Lynn Pettis (9/19/2012)

---

opc.three (9/4/2012)

---

Jeff Moden (9/4/2012)

---

opc.three (9/4/2012)

---

All sysadmins can execute any commands they wish and those commands will run in the context of the SQL Server service account, i.e. you...

Jeff Moden (9/18/2012)

---

And some folks wonder why I/O is one of the biggest bottle-necks on some servers. Imagine what it would cost to get a 300% improvement by changing...

Happy you got something going. I didn't mention tail.exe because it's not technically a PowerShell solution, but if you're open to using an external exe here is a sourceforge project...

Jeff Moden (9/19/2012)

---

Sorry, lost track of this thread...

opc.three (9/5/2012)

---

Jeff Moden (9/5/2012)

---

Examples of why I'd want to use xp_CmdShell are two fold.

The first is cost. It's not likely...

Fly Girl (9/17/2012)

---

Windows Server 2008 R2

I'm totally new to PowerShell but was trying to use it to solve an issue with data files that come with the last row being...

Dynamic SQL does break the ownership chain established when exectuing the proc. A new ownership chain can be established later in the call stack but at the end of the...

Thanks for posting back the root cause so others can benefit. The Excel driver built-into SSIS is a 32-bit Jet 4.0 driver which cannot be used in 64-bit mode so...

What build are you on?

Perry, I am quite certain...

Thank you. This confirms what was mentioned before. At present there are no indicators that anything out of the ordinary is occurring in terms of how much...

All we have established so far is that your SQL Server eventually...

Thanks for posting some results but now that we know you have lock pages in memory (lpim) enabled the process list is not going to tell us anything of much...

Chances are you have 'lock pages in memory' enabled which prevents memory SQL Server allocates to the buffer pool from showing in Task Manager. Same symptoms: http://www.sqlservercentral.com/Forums/FindPost1356979.aspx