Viewing 15 posts - 19,786 through 19,800 (of 59,098 total)
To see more about how the CROSSTAB code above works, please see the following article...
http://www.sqlservercentral.com/articles/T-SQL/63681/
To see how to do it without having to know the number of years, please see...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2015 at 5:01 pm
sgmunson (8/25/2015)
Rod at work (8/24/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2015 at 4:57 pm
It may also be that the data has grown and there's simply not enough memory to do what you want.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2015 at 4:32 pm
rob.lewis 86087 (7/2/2015)
One has a function, the other has the tables and views
using dba
select dbo.function(t.column) as x from dbb.dbo.table as t
gives m an...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2015 at 4:01 pm
ChrisM@Work (8/25/2015)
Hi JoshIIRC a hard tally table is usually slightly faster than an inline one. Google will tell you for sure.
No need to Google. Here's a chart from the...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2015 at 9:40 am
greg.bull (4/27/2015)
In essence to combine these:
'font/@color' = case...(set up to return...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2015 at 9:26 am
Just an added tip...
This...
and DOB is not null
and DOB <>''
... is the same as this...
and DOB > ''
... and can sometimes be a fair bit faster. It works because...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2015 at 7:34 pm
If the reboot fixes the problem, I strongly suspect some pretty nasty parameter sniffing. My first step would be to clear cache prior to doing the cube rebuilds. ...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2015 at 7:29 pm
halifaxdal (9/15/2010)
I know there are lots of useful script/approaches on how to send out HTML email from SQL, one particular situation I am having is: is it possible to...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2015 at 7:22 pm
MAK-1128556 (8/18/2009)
Thanks, so there is any script we have to find out how many indexes need to be defragment
Yes. Lookup [font="Arial Black"]sys.dm_db_index_physical_stats [/font]and [font="Arial Black"]ALTER INDEX[/font] in Books Online...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2015 at 7:12 pm
djackson 22568 (8/24/2015)
Except that to continue the analogy, you also have to worry about the people who keep walking under you, seeing the safety net and packing it up, moving...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2015 at 5:25 pm
GilaMonster (8/24/2015)
James_R_Alves (8/24/2015)
There may be a performance benefit to using table vars over # temp tables as well.A negative one usually, due to the lack of statistics.
...and execution plan estimates...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2015 at 1:03 pm
You might also try using ALTER INDEX instead of DBCC DBREINDEX, which has been deprecated.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2015 at 12:48 pm
Steve Jones - SSC Editor (8/24/2015)
Jeff Moden (8/21/2015)
Heh... who tests the unit test code to make sure that's right? 😉
The developer, other developers, whoever. If it's not, change it. Tests...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2015 at 11:58 am
Heh... perhaps a better question would be, "Are any of you good folks doing penetration testing of your apps and/or your database servers"?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 24, 2015 at 11:34 am
Viewing 15 posts - 19,786 through 19,800 (of 59,098 total)