http://sqlknowitall.com/
If there are not enough groups to meet n, it will increase until there are no more rows leaving n-totalGroups not included in the values of the result set. This means that if you add a new data file to a filegroup that has mostly full data files, the proportional fill weightings will be such that the new file will be the one where allocations come from until it fills up to the same level as the older files
http://blog.sqlauthority.com/2007/06/08/sql-server-insert-multiple-records-using-one-insert-statement-use-of-union-all/
you need to have one table that stores personal details, lets say TableA Another table that stores Test results, lets say TableB Another table that stores Medicines, lets Say TableC And one common key that joins these tables, meaning implementing one to many relation ship, by creating foreign key constraints on tables. On the same DB I m running another insert query using Union all to insert data in 11 columns this is taking 1 sec for 1000 records but other query which is inserting data in 20 columns taking 5 sec
http://scn.sap.com/community/sqlserver/blog
To make sure I do not miss any of them I keep looking for SAP documentation, SAP notes, blogs on SCN and the SAP on SQL Server section of MSDN before I start with a new migration. For the system databases (Master, Model, and MSDB), I recommend daily backups.Under Frequency, for Occurs: select Daily.Under Daily frequency, for Occurs once at: set an appropriate time (e.g
http://sqlserver-qa.net/2012/09/02/sql-server-configration-settings-maxdop-to-be-or-not-to-be/
But in our case it did not made any difference in query execution results and we had to set the MAXDOP to 4 as the server CPU configuration was 4 * 16 core! I have written few recipes with regard to SQL Server configuration practices on my book titled: SQL Server 2008 R2 Administration cookbook. Within the data warehousing (OLAP) design by default SQL Server uses majority of available cores as the queries are complex with many joins and dealing with large amounts of data
http://sqltwist.com/?p=9
As seen below, the ClickOnce Application Deployment Manifest files are located in the ReportBuilder directory for both Report Builder 1.0 and Report Builder 3.0. Disk Queue Length represents the average number of physical read and write requests that were queued on the selected physical disk during the sampling period
SQL TWIST - This Week in SQL Server Technology
http://sqltwist.com/
If you ever needed to determine how many VLFs are within a database you can run DBCC LOGINFO from within the context database and the total number of rows returned would give you your VLF account. Essentially having too many VLFs can affect performance of any activity that reads from the transaction log such as Replication, AlwaysOn Availability Groups, Mirroring, Database Recovery etc
How and when to restrict parallelism in SQL Server
http://searchwindowsserver.techtarget.com/tip/How-and-when-to-restrict-parallelism-in-SQL-Server
Five most useful Windows Sysinternals tools Sysinternal utilities such as AccessChk and Handle can target specific problem areas in your Windows OS, including identifying ... SQL Server does do a good deal of auto tuning (i.e., it spawns less parallel queries if CPU usage is high), but it cannot always predict when something is going to wind up running slower or less efficiently in multiple threads
http://www.microsoft.com/en-us/server-cloud/
Discover what Cortana Analytics can do for your data Bring your data to life and spot trends with Microsoft Power BI Power BI transforms your company's data into rich visuals so you can focus on what matters to you
performance - SQL Server 2012 slower than 2008 - Database Administrators Stack Exchange
http://dba.stackexchange.com/questions/35579/sql-server-2012-slower-than-2008
The bottom scans have a slightly different row number (not significant) but quite different costs: old is 2.49884 (IO 2.28979 CPU 0.20905) vs new 1.59109 (IO 1.53868 CPU 0.0524084). You want your MAXDOP setting to match the number of cores per NUMA node to minimize the number of times a given numa node needs to go outside its own memory for data
http://www.brentozar.com/archive/2013/09/five-sql-server-settings-to-change/
For example, on any server I manage, I like to have a particular vendor app that does a phenomenal job of correlating plan cache changes to database object changes. Regarding the MAXDOP, I would say that according to the Microsoft KB you should to check how many cores per NUMA Node you have, and then you should set the MAXDOP to this maximum value or less
http://www.microsoft.com/en-us/server-cloud/products/sql-server-editions/
Learn more Standard SQL Server Standard provides core data management and business intelligence capabilities for non-critical workloads with minimal IT resources. Back to top Other editions Compact edition Microsoft SQL Server Compact edition is a free, embedded database that software developers can use for building ASP.NET websites and Windows desktop applications
Some Suggested SQL Server 2008 R2 Instance Configuration Settings - SQLServerCentral
http://www.sqlservercentral.com/blogs/glennberry/2011/02/25/some-suggested-sql-server-2008-r2-instance-configuration-settings/
The idea here is to limit how much memory the buffer pool can use in order to avoid starving other SQL Server components or the operating system for memory. With OLTP workloads, sometimes the Query Optimizer will choose a parallel query plan when a non-parallel query plan would have actually have been less expensive
TIP: Setting SQL Max Degree of Parallelism Achieve Big System Center SQL Performance Gains - System Center Central
http://www.systemcentercentral.com/tip-setting-sql-max-degree-of-parallelism-achieve-big-database-performance-gains/
Press Alt-Shift-H for help","You have unsaved changes are you sure you want to navigate away?":"The changes you made will be lost if you navigate away from this page.","Your browser doesn't support direct access to the clipboard. What is the max degree of parallelism? The Microsoft SQL Server max degree of parallelism (MAXDOP) configuration option controls the number of processors that are used for the execution of a query in a parallel plan
http://blogs.msdn.com/b/saponsqlserver/archive/2015/04/29/max-degree-of-parallelism-maxdop.aspx
Based on those checks, a query might not be executed using all CPU threads available, instead using only a few CPU threads (or even just one CPU thread). For example, parallel queries performing small joins and aggregations on small data sets can become inefficient when they run on all 64 CPU threads of a server
http://blogs.msdn.com/b/jimmymay/archive/2008/11/28/case-study-part-1-cxpacket-wait-stats-max-degree-of-parallelism-option-introduction-to-using-wait-stats-to-identify-remediate-query-parallelism-bottlenecks.aspx
This allows the SQL Server engine to know how many concurrent IO can be issued while maintaining low latency, without relying entirely on the disk access time feedback. If IO is throttled, then the full IO performance capability of the disk system is not realized." See my next post, part 2 of this 4-part series, to see the effects of changing the max degree of parallelism option from the default value of 0 to 1
No comments:
Post a Comment