afernandez
-
@ wouldn't lie to you bro
about 16 hours ago
from TweetDeck
in reply to SQLSarg
-
@ It's not SQL Server, it's you ;)
about 16 hours ago
from TweetDeck
in reply to SQLSarg
-
@ Thanks, sent them an email. I hope they take me in.
12:52 PM Dec 11th
from TweetDeck
in reply to unclebiguns
-
@ how do I join?
12:38 PM Dec 11th
from TweetDeck
in reply to unclebiguns
-
@ frio? nada que ver.
12:20 PM Dec 11th
from TweetDeck
in reply to circunflejo
-
@ no prob, happy to help...btw I always find something new in the product. Pretty much everyday.
11:36 AM Dec 11th
from TweetDeck
in reply to ScottStonehouse
-
@ in SSMS, go to SQL Server Agent -> Proxies -> Powershell, that's where you create one for Powershell job steps.
11:30 AM Dec 11th
from TweetDeck
in reply to ScottStonehouse
-
@ did you configure a proxy account for that?
11:23 AM Dec 11th
from TweetDeck
in reply to ScottStonehouse
-
@ it just helps pinpoint the source of the problems so much faster.
7:56 AM Dec 11th
from TweetDeck
in reply to GarethSwan
-
@ totally worth the $$
7:53 AM Dec 11th
from TweetDeck
in reply to GarethSwan
-
@ oh ok, that's better now ;)
7:24 AM Dec 11th
from TweetDeck
in reply to SQLChicken
-
@ first, Lady Gaga. Now Amadeus. What next, Spice Girls?
7:16 AM Dec 11th
from TweetDeck
in reply to SQLChicken
-
Mozilla team member recommends Bing over Google, citing privacy concerns after Schmidt's comments
6:51 AM Dec 11th
from TweetDeck
-
@ ha!
6:33 AM Dec 11th
from TweetDeck
in reply to unclebiguns
-
@ Good point, small detail :)
12:43 PM Dec 10th
from TweetDeck
in reply to cfrandall
-
@ Divide and conquer. Get to the Mississippi river first :)
12:12 PM Dec 10th
from TweetDeck
in reply to cfrandall
-
@ not sure you would make it swimming. Need a raft. Or an amphibious vehicle.
12:01 PM Dec 10th
from TweetDeck
in reply to cfrandall
-
@ and yes...the server had 11 traces running on it. I'm gonna go visit my support guys with a flamethrower.
11:33 AM Dec 10th
from TweetDeck
in reply to WesleyBackelant
-
@ Thanks! Good old MTL. I guess a restart is in order. Likely MTL fragementation -- has happened to us before.
11:31 AM Dec 10th
from TweetDeck
in reply to WesleyBackelant
-
Got a "Not enough memory was available for trace" error w/ profiler on SQL 2005 x86 SP3. Queries are being serviced. Help?
11:19 AM Dec 10th
from TweetDeck
|
- Name Argenis Fernandez
- Location South Florida
- Web http://www.sqlps.com
- Bio SQL Server Technology Owner for a cutting-edge SaaS company. Powershell junkie.
|
