Viewing 15 posts - 15,991 through 16,005 (of 59,067 total)
Luis Cazares (12/30/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2016 at 7:38 am
southernnevada99 (12/28/2016)
I am exporting data from sql2012 into excel sheet...
HOW are you doing the export and what format are you using? For example, are you using CSV/TSV or what?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2016 at 7:36 am
There are a couple of issues that are just wasting a lot of CPU time.
The first is the problem of the store procedure variables that involve dates being setup as...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2016 at 7:33 am
ThomasRushton (12/30/2016)
What is this, a free consultancy?http://www.sqlservercentral.com/Forums/Topic1846082-2799-2.aspx
Strewth. Where's my popcorn?
No. It's someone with a very appropriate login handle.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2016 at 5:53 am
Possibly out of date stats on the source? Maybe parameter sniffing? Maybe someone had a long winded transaction on one of the underlying tables of the view?
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2016 at 10:55 pm
Yes. First, see my original post on the subject from 2007 so you get the big picture of what was requested so that you'll understand the following code, which...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 29, 2016 at 10:33 pm
@pankaj.chakole,
My apologies. I got caught up in the moment because of a different thought process than most. Like I said, I wouldn't use Extended Events for this particular...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2016 at 7:36 pm
chuck.forbes (12/28/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2016 at 4:51 pm
kevinH-1006814 (7/27/2009)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2016 at 4:20 pm
lmarkum (12/23/2016)
This problem is occurring on a SQL Server 2012 Standard instance that is on SP1.
There were some really nasty problems in SQL Server 2012 prior to SP3. Things...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2016 at 4:16 pm
IIRC, PARSENAME has an element length of NCHAR(128) as a limit on each part it returns and is heavily dependent on the consistent position of items but the following is...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2016 at 4:12 pm
chuck.forbes (12/28/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2016 at 4:04 pm
peter 67432 (12/28/2016)
- I search on (like?) 921996 it will find the record with 92.1996 or 1219!96
Is there...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2016 at 9:45 am
Database admin(DBA) (12/28/2016)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2016 at 9:43 am
Heh... I sometimes can't remember what I had for dinner last night but I remembered this. Strange how the mind works... or sometimes doesn't.
--Jeff Moden
Change is inevitable... Change for the better is not.
December 28, 2016 at 9:22 am
Viewing 15 posts - 15,991 through 16,005 (of 59,067 total)