concept Windows in category sql

This is an excerpt from Manning's book SQL Server MVP Deep Dives Vol. 2.
Correcting disk alignment in Windows Server 2008 and later is much easier than using the diskpart.exe or diskpar.exe command-line applications. When new partitions are created in Windows Server 2008, they’re aligned automatically, but Windows aligns the volumes at the 1024k boundary instead of the 64k boundary. Microsoft made the decision for this 1 MB alignment instead of a 64k alignment to be compliant with all possible storage solution architectures. When using a storage array with a 64k block size, this 1M alignment won’t affect performance. You may notice that slightly less than 1 MB of space is missing from the volume, instead of the 64k of space missing that you might otherwise see.

This is an excerpt from Manning's book SQL Server MVP Deep Dives.
Replacement sets, the next section, are something you’ll use less often. With replacements, SQL Server doesn’t look for the word in the <pat> (pattern) tag; instead it looks for the word in the <sub> tag. In this case, if a user types in W2K, the full-text search engine will instead look for Windows 2000. One true-life situation I can think of where this would be useful is addresses. If you know your system converts all street or state abbreviations to their full expanded name, then you could use this as a trap with full-text searching. For example:
To get useful information about your SQL Server’s behavior, you need to combine the use of both PerfMon and Profiler (server-side traces are a good alternative to Profiler). That’s because of the fundamental nature of each tool. PerfMon is great at showing the overall resource consumption of most every area of Windows and of SQL Server. Profiler, on the other hand, shows you specific events as they occur (or fire) inside the SQL Server. By combining the output of both tools, we get a great view of overall resource consumption and the individual SQL Server events that are causing that resource consumption. When resource consumption, say CPU or Disk I/O, gets unacceptably high, we can tell exactly what statement, batch, or job caused it. That way, we know exactly where to focus our attention when rewriting or tuning a particular SQL Server activity.
Listing 6. Output from running listing 5
name description ----------------------- ------------------------------------------------ etw_classic_sync_target Event Tracing for Windows (ETW) Synchronous Target synchronous_bucketizer Synchronous bucketizing target asynchronous_bucketizer Asynchronous bucketizing target asynchronous_file_target Asynchronous file target pair_matching Pairing target synchronous_event_counter Synchronous Counter target ring_buffer Asynchronous ring buffer target.