Viewing 15 posts - 2,266 through 2,280 (of 8,416 total)
Gianluca Sartori (12/20/2010)
I installed the product around 1 month ago and I got something like 4 updates. Looks like they're still working on it.
Yep. I'm looking forward to regular...
December 20, 2010 at 1:45 am
UMG Developer (12/18/2010)
As long as you understand the consequences and limitations...
I like to think I have a fairly good grasp, yes.
...and the optimizer can create decent plans with the row...
December 18, 2010 at 8:06 pm
UMG Developer (12/18/2010)
December 18, 2010 at 7:38 pm
ALZDBA (12/18/2010)
No. Twitter says "user unknown". Thats why I posted the remark.
That's annoying. I did check at the time I made the change, and it did work - must...
December 18, 2010 at 9:37 am
ALZDBA (12/18/2010)
Hey .. paulwhitenz also disappeared at SSC.:hehe:Welcome SQLkiwi 😀
Keep in mind to have SSC altering your twitter refs in your articles 😉
Thanks, though the old twitter references will...
December 18, 2010 at 7:07 am
I took a stab at 1,30. So it was 1,*. Ha, very good. I'll have forgotten this again in half an hour, and I still won't care...
December 18, 2010 at 6:34 am
SanDroid (12/14/2010)
Nils Gustav Stråbø (12/14/2010)
vk-kirov (12/14/2010)
The bad news is that, according to BOL, "this view is applicable only to the tempdb database".
I would not expect much change in SGAM pages...
December 18, 2010 at 6:30 am
I am slightly confused as to what is meant by a 'simply named' temporary table in the preceding discussion.
Strikes me this is a great reason to use table variables instead...
December 18, 2010 at 6:20 am
My first impressions of SQLcomplete are that it is quite usable, and annoying in different ways from standard IntelliSense.
It's a very new product, and will no doubt be much better...
December 18, 2010 at 4:24 am
SQL Server 2008 onwards adds ISO_WEEK to the range of acceptable DATEPARTs:
SELECT DATEPART(ISO_WEEK, CURRENT_TIMESTAMP);
SELECT DATEPART(WEEK, CURRENT_TIMESTAMP);
In 2005, you would have to write your own implementation.
More information: http://msdn.microsoft.com/en-us/library/ms174420(v=SQL.100).aspx
December 18, 2010 at 4:21 am
Gail was just giving a brief high-level overview in that link you posted.
Missed reads are possible at REPEATABLE READ, and a scan at READ UNCOMMITTED does not always use an...
December 18, 2010 at 2:48 am
Craig Farrell (12/17/2010)
<--------------------------- This look on my face is getting to be a habit these past two weeks...
Cool avatar, much better than the last one IMVHO.
Okay, that explains why...
December 17, 2010 at 5:25 pm
Lamprey13 (12/17/2010)
To add to Pauls links, here is a link of links.. 😉http://sqlserverpedia.com/blog/sql-server-bloggers/merry-go-round-scans/
My problem with the Advanced Scan feature is that, like Gail, I have been unable to reproduce it....
December 17, 2010 at 5:13 pm
Lamprey13 (12/17/2010)
Interesting, can you produce a NULL by using something other than the RAND() function?
Sure. That's was just a compact way to demo the issue. Pretty much any...
December 17, 2010 at 4:50 pm
Viewing 15 posts - 2,266 through 2,280 (of 8,416 total)