THE SQL Server Blog Spot on the Web

Welcome to - The SQL Server blog spot on the web Sign in | |


You searched for the word(s):
Showing page 1 of 56 (552 total posts) < 1 second(s)
  • Samsung SSD 960 PRO - 3500MB/s

    Last month, Samsung announced that their 960 Pro, (PCI-E x4 gen3) M.2 NVMe SSD would available in October at 512GB, 1TB and 2TB capacities. This is a high-end PC and workstation product. There is a similar but separate product line (SM961?) for OEM customers. The 960 Pro had already been mentioned earlier this year. This week, all the ...
    Posted to Joe Chang (Weblog) by jchang on October 19, 2016
  • re: Job History row limiter

    I am inclined to recommend modifying sp_sqlagent_log_jobhistory to comment out the call to sp_jobhistory_row_limiter, then once a night or some interval, delete the excess rows from msdb.dbo.sysjobhistory using whatever criteria you might like. As for sp_sqlagent_has_server_access, my guess is that your jobs are running from an account that has ...
    Posted to Joe Chang (Weblog) by jchang on October 18, 2016
  • re: Keep more history for your Agent jobs

    In my case, the issue was not that the sp_jobhistory_row_limiter call consuming too much cpu, but rather that it was enough to show up on the top 10-20 list. For all normal code, I had made substantial improvement, and I did not want to say this is MS code that we cannot touch, when in fact we can touch it. My assessment was that adhering to the ...
    Posted to Tibor Karaszi (Weblog) by jchang on October 17, 2016
  • re: Keep more history for your Agent jobs

    every time a job executes, the procedure sp_sqlagent_log_jobhistory is called to record the fact. this procedure, at the end, calls sp_jobhistory_row_limiter. if you look at the procedure, there is a moderate to significant overhead depending on the circumstances, in the post ...
    Posted to Tibor Karaszi (Weblog) by jchang on October 16, 2016
  • re: Passwords – a secret you have no right to share

    there are 3 levels of password security 1) low - easily guessed 2) medium - somewhat difficult to remember, write it down on a yellow sticky, stick on back of monitor 3) high - difficult to remember, write it on a yellow sticky, stick on front of monitor
    Posted to Rob Farley (Weblog) by jchang on October 12, 2016
  • re: Insert Performance Limitations with Sequentially Increasing Index

    Henrik, if you have a link for the 2011 article, please let me know and I will put it in the body above for reference. A SQL Server Latch uses a lightweight synchronization mechanism, I believe it is used only for reads. It does not have the mechanisms to support SQL writes? SQL Server write operations need locks, which are more expensive than ...
    Posted to Joe Chang (Weblog) by jchang on October 10, 2016
  • Insert Performance Limitations with Sequentially Increasing Index

    Earlier this year, HPE and Microsoft sponsored an article, The Importance of Benchmarking, in SQL Server Pro. While true, it is also apparent that there has been little interest in benchmarks within the DBA/IT community over the last several years. There are many reasons for this, one of which is the emphasis on the benchmark result ...
    Posted to Joe Chang (Weblog) by jchang on October 9, 2016
  • re: Enterprise Storage Systems - EMC VMAX

    its been very many years since I was last allowed to connect to the VMAX as administrator. Still, this is puzzling to me. Even if you saturate the FC connections on the host (storage client), chances are that you are not saturating the FC ports on the SAN. Typically there might be 2, 4 or 8 FC links from the host to the FC switches, but there ...
    Posted to Joe Chang (Weblog) by jchang on September 30, 2016
  • re: SQL Server on Xeon Phi?

    the Xeon Phi is not cheap. It may be cheap to build a chip with 4-8 Atom cores, building a giant die is not. Networking cheap computers only works for workloads that can tolerate high latency. As I said above, the nature of Moore's Law is that a complex core does not have linear gain with the number of transistors. Some workloads really need a ...
    Posted to Joe Chang (Weblog) by jchang on August 30, 2016
  • re: SQL Server on Xeon Phi?

    The objectives for the current Xeon Phi is proof-of-concept. That the smaller/simpler Atom core at 1.3GHz are not far off the powerful Broadwell cores at 2-3GHz+ in transactional queries, with the expectation that Broadwell at 3GHz+ are exception for code running largely inside L2 cache. Also, for transactions, SMT should be more than 2-threads ...
    Posted to Joe Chang (Weblog) by jchang on August 24, 2016
1 2 3 4 5 Next > ... Last »
Privacy Statement