Viewing 15 posts - 27,106 through 27,120 (of 59,101 total)
My application started to report random connection failures.
We've had similar problems in the past. A good number of them turned out to be that the device was setup with...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2013 at 4:56 pm
LutzM (3/11/2012)
I use it to identify if an applicant
- prefers using a set or loop based method where both methods are possible
- knows enough T-SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2013 at 4:44 pm
Other than finding a sponsor, I have no idea but anyone with an MCM should be given a whack at it. Hopefully, my response will serve as a "bump"...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2013 at 4:38 pm
BWAAA-HAAAA!!! Oddly enough, that's exactly what I see when I look at some resumes.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2013 at 4:31 pm
Sean Lange (4/1/2013)
Your data is not normalized and your results are not normalized. The reason this is difficult is because your structures make this difficult.
Heh... I can't help wondering if...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2013 at 4:21 pm
umarrizwan (4/1/2013)
SELECT DISTINCT V.CERTYEAR,(SELECT SUM(QUATITY) FROM VCERTS WHERE CERTYEAR=V.CERTYEAR AND CERTCODE='HI-MASTER')QTYMASTER,
(SELECT SUM(QUATITY) FROM VCERTS WHERE CERTYEAR=V.CERTYEAR AND CERTCODE='HI-INSTR')QTYINSTR,
(SELECT SUM(QUATITY) FROM VCERTS WHERE CERTYEAR=V.CERTYEAR AND CERTCODE='HI-TRAIN')QTYTRAIN
FROM DBO.VCERTS V
ORDER BY 1
4 Hits...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2013 at 4:15 pm
AndrewSQLDBA (4/1/2013)
SQL Server does not Loop thru rows. SQL Server is Set Based.Please do not indicate that a database loops thru rows.
Andrew SQLDBA
Certainly not in the classical sense, but SQL...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2013 at 3:56 pm
sqlfriends (4/1/2013)
Grant Fritchey (4/1/2013)
Glad to hear it's fixed.Just curious though, why not use a PowerShell type of step in SQL Agent for a PowerShell script?
I found it runs much faster...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2013 at 3:48 pm
With the understanding that I've not tried it, couldn't you put a TRY/CATCH in the trigger to ignore all but the most fatal of errors?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2013 at 3:44 pm
elg (4/1/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
April 1, 2013 at 3:27 pm
jfogel (3/30/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2013 at 7:04 pm
Then I have to admit, points in favor of PowerShell but only if such auditing software is actually inplace, active, and that, you as an administrator, can't defeat the software...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2013 at 4:38 pm
Ok. So let's ask another question. To keep it simple, you've either been given administrative privs on a box or you are the administrator. You fire up PowerShell...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2013 at 2:22 pm
Very cool, JLS!
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2013 at 1:26 pm
gurjer48 (3/30/2013)
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2013 at 1:25 pm
Viewing 15 posts - 27,106 through 27,120 (of 59,101 total)