SQL Update Statement - Latest Comments

Re: Presentations

AWSOMEDEVSIGNER — Tue, 15 May 2012 12:26:33 -0000

Thank you! This stuff is really useful!

Re: SQL Server 2012: Biggest Little Core-house

Steve Jones — Mon, 30 Apr 2012 14:59:32 -0000

This is confusing as heck, and I'm not sure I've got it straight. It would be nice to see you list out 12 scenarios and show the upgrade cost/use. Say I have a 16 core system, a 20 core system, a 24 core system, licensed different ways with new and upgrade (SA and non-SA) paths being taken.

Re: SQL Server 2012: Biggest Little Core-house

Brent Ozar — Mon, 30 Apr 2012 09:39:46 -0000

Aaron is totally right - major typo on my part there. It should definitely say "by the CAL".

Re: SQL Server 2012: Biggest Little Core-house

Aaron Bertrand — Mon, 30 Apr 2012 09:36:34 -0000

Hmm, I'm not sure I agree with Brent's edit. If you buy SQL Server 2012 licensed by the core, SQL Server *will* use all the cores. The 20-core limit comes into effect when you use VL or other pre-pidded builds where it is known that SQL Server is actually using CAL licensing (and you can only get these builds through SA, if you had CAL licensing on a previous version of SQL Server Enterprise that is still covered by SA).

Re: SQL Server 2012: Biggest Little Core-house

Brent Ozar — Mon, 30 Apr 2012 09:20:14 -0000

Just to clarify - you need to change this sentence: "if you have a server with 4 8-core processors for a total of 32 cores,
and you install SQL Server 2012 on it, SQL Server will only “see”/use 20
of those cores"

To instead say: "if you have a server with 4 8-core processors for a total of 32 cores,
and you install SQL Server 2012 on it licensed by the core, SQL Server will only “see”/use 20
of those cores

Re: SQL University

Shahbaz Ali — Wed, 11 Apr 2012 10:16:17 -0000

hi.....

Re: STOP! Consolidate and Listen

SQLRook — Mon, 26 Mar 2012 10:09:47 -0000

Thanks for Killin my Brain Like A Poisonous Mushroom! Word to your Mother!

Re: STOP! Consolidate and Listen

SQLChicken — Wed, 21 Mar 2012 06:31:33 -0000

Thanks Rob! No worries, your spirit lingered and powered me through the early morning grog :-)

Re: STOP! Consolidate and Listen

Rob Farley — Wed, 21 Mar 2012 06:24:37 -0000

Thanks Jorge - by all accounts you did really well. Sorry I couldn't hang around longer.

Re: Monday Morning Mistakes: Not Setting Memory Limits

SQLChicken — Wed, 14 Mar 2012 09:37:07 -0000

Very cool Rudy, thanks for the link to your article!

Re: Monday Morning Mistakes: Not Setting Memory Limits

Rudy Panigas — Wed, 14 Mar 2012 09:32:56 -0000

Nice article. It so true about DBAs not setting memory setting and just using the default. I have written an article/code on SQL Server Central ( http://www.sqlservercentral.co... ) that has can be used to determine the max memory setting. Just execute the script and it will display your current memory and recommended max memory setting. Just another way of trying to make things easier for DBAs everywhere.

Thanks,

Rudy

Re: Monday Morning Mistakes: Not Setting Memory Limits

dvroman — Mon, 12 Mar 2012 10:52:22 -0000

How about a Saturday night mistake. One of our processes is set to run a 02:10. It was skipped because that time didn't exist. Daylight savings time.

Re: Monday Morning Mistakes: Not Setting Memory Limits

Sandra — Thu, 08 Mar 2012 15:59:20 -0000

Yup. It's a lot of different problems. :-) But, at minimum, I wanted an idea of how to configure memory when a number of components were on the same machine. If we move to a new production server, it'll probably be the engine and SSAS at least on one server. So, thanks for the thoughts on this.

Re: Monday Morning Mistakes: Not Setting Memory Limits

SQLChicken — Thu, 08 Mar 2012 14:39:30 -0000

Ouch! That sounds like a slightly different problem. Question is, why did they try to cram all that crap (SharePoint, SSIS, SSRS, SSAS) on a single VM with only 4 GB of memory? Also why cap at 4GB if you can go more on 64-bit? The other fun tidbit there is that SharePoint has very specific settings/configurations you need to setup in order to be supported by Microsoft. Check out this capacity planning and configuration guide:
http://technet.microsoft.com/e...

Re: Monday Morning Mistakes: Not Setting Memory Limits

Sandra — Thu, 08 Mar 2012 12:35:53 -0000

The current VM is a 64 bit server on Win2008 SP2. It was originally a "dev" server where the developer installed TFS. So, SQL, SSIS, SSRS, SSAS and some Sharepoint were all installed on the 40 GB C: drive. Zoom forward a few months and it finally comes to my attention since they want to call it production now. This TFS install supports about 4 full time programmers and 2 occasional programmers. The DB are fairly small. I'm guessing the engine has the most work.

I'm hoping to get them to migrate the necessary components to a real production server and utilize our existing SSRS server. It's sort of a crazy mess. Thanks for info.

Re: Monday Morning Mistakes: Not Setting Memory Limits

SQLChicken — Thu, 08 Mar 2012 10:26:53 -0000

Sandra, that's a bit of "it depends" answer (I know, nobody likes to hear it). Is that an isolated VM/server or are those running on a laptop? Also for 4GB seems quite small, are you running 32-bit OS? Since 32-bit is quite limited I'd be pretty conservative with allocations. Maybe 1-1.5 GB for engine, SSAS low limit to 0 and upper limit to 20-30% (again here it depends, how often are you processing/reporting from cubes?). Also fun fact from SSAS Operations Guide:

Analysis
Services does not use the AWE API to allocate memory, which means that on
32-bit systems you are restricted to either 2 GB or 3 GB of memory for Analysis
Services.

Source: http://msdn.microsoft.com/en-u...

Basically allocate as your needs see fit. If you're doing more engine work, allocate a bit more to that. But also remember to keep enough memory available so that you don't starve the OS. And finally, if you're on 32-bit please PLEASE start moving your systems to 64-bit ;-)

Re: Monday Morning Mistakes: Not Setting Memory Limits

Sandra — Wed, 07 Mar 2012 18:40:35 -0000

Any recommendations if you have the database engine, SSAS, and SSRS all on the same VM (for TFS) with 4 GB configured?

Re: Monday Morning Mistakes: SSIS Expressions Not Evaluating Correctly

Jorge Segarra — Mon, 20 Feb 2012 12:59:29 -0000

I thought you guys had put that in. I could've sworn both our products had that behavior put in. Will need to test it on system that doesn't have BIxPress on it.

Re: Monday Morning Mistakes: SSIS Expressions Not Evaluating Correctly

Greg Galloway — Sun, 19 Feb 2012 21:44:36 -0000

Are you sure? I don't recall we put that in BIDS Helper.

Re: Starting the SQL Journey: Part II

Tanner — Sun, 19 Feb 2012 09:26:47 -0000

Another good SQL tutorial to learn the basics from is http://www.1keydata.com/sql/sq...

Re: Monday Morning Mistakes: SSIS Expressions Not Evaluating Correctly

Jorge Segarra — Thu, 16 Feb 2012 15:52:22 -0000

Yes, 3rd party tools like BIDS Helper and BIxPress make that change for you automatically. That's one of their selling points.

Re: Monday Morning Mistakes: SSIS Expressions Not Evaluating Correctly

Gary Wilson — Thu, 16 Feb 2012 13:59:47 -0000

I have never set the EvaluateAsExpression to true myself but all my expressions work so BIDS Helper must be doing it for me.

Re: Monday Morning Mistakes: SSIS Expressions Not Evaluating Correctly

Carla Sabotta — Tue, 14 Feb 2012 04:06:56 -0000

No problem. :-)

Re: Monday Morning Mistakes: SSIS Expressions Not Evaluating Correctly

Jorge Segarra — Tue, 14 Feb 2012 02:17:37 -0000

Thanks but that still doesn't apply to the issue I'm presenting. I wasn't addressing data types, I was demonstrating the fact that the expression won't be evaluated without that property of EvaluateAsExpression being set to true.

*edit: rereading comment and realized I think you were just adding more helpful details around the properties of a variable. Thanks for providing more helpful resources and sorry if my last comment came off snappier than I meant to

Re: Monday Morning Mistakes: SSIS Expressions Not Evaluating Correctly

Carla Sabotta — Mon, 13 Feb 2012 21:47:03 -0000

When the value of the variable is set by an expression, the ValueType property is automatically updated to a data type that is compatible with the evaluation result of the expression. For example, if the Value property contains 0 and ValueType property contains Int32, and you then set Expression to GETDATE(), the Value property now contains the current date and time and ValueType is set to DateTime. For more information, see How to: Set the Properties of a Variable at http://msdn.microsoft.com/en-u... .

For expression examples, see SSIS Expression Cheat Sheet (http://pragmaticworks.com/chea... and SSIS Expression Examples ( http://social.technet.microsof....