SQLRNNR (5/22/2015)

---

IMHO - those recommendations are the lowest common denominator if you MUST have...

Brandie Tarvin (5/22/2015)

---

They kind of look like smoke detectors, usually installed in the ceiling tiles. They cover about a...

noise

Grant Fritchey (5/22/2015)

---

Question for the crew since this is a fairly international audience, plagiarism

I understand that some cultures look at it very differently than most Western European-based ones do. There's...

GilaMonster (5/22/2015)

---

Yes, excellent idea, just go and change max server memory from ~28 GB with SQL using all of it down to 4GB and back up because that 95% figure...

Quick question, is there a dinosaur in the decision making team, haven't seen this kind of architecture since AS/400?

😎

Quick note, if manually setting the...

GilaMonster (5/22/2015)

---

Please, stop fiddling with the memory. From the symptoms, stats and details you've posted, the memory is NOT the problem. At most it's a symptom of the problem, a...

Bugger

Quick thought, normally use sys.dm_exec_describe_first_result_set and build the dataflow based on the output.

😎

Quick question, can you post the output of these two queries?

😎

SELECT

OSM.total_physical_memory_kb

,OSM.available_physical_memory_kb

,OSM.total_page_file_kb

,OSM.available_page_file_kb

,OSM.system_cache_kb

,OSM.kernel_paged_pool_kb

...

You are most welcome.

😎

As always Alwin:-D

😎

Just one step left

😎

USE TEMPDB;

GO

SET NOCOUNT ON;

DECLARE @MY_TIME VARCHAR(100) = '2015-01-16T00:00:00.000-06:00';

SELECT CONVERT(DATETIMEOFFSET,@MY_TIME,127);

SELECT CONVERT(DATETIME,CONVERT(DATETIMEOFFSET,@MY_TIME,127),0);

Just realized that the target data type must be DATETIMEOFFSET, otherwise it will throw errors in any conversion

😎

USE tempdb;

GO

SET NOCOUNT ON;

DECLARE @MY_TIME VARCHAR(100) = '2015-01-16T16:06:14.577-06:00';

SELECT CONVERT(DATETIMEOFFSET,@MY_TIME,127)