G->TechLink: G->Pointer's Technology Link

Sizing discussions can range from exact numbers to the vague statement of "it depends [on the usage/applications/...]". But even an "it depends"-discussion has to start with some bare numbers as a basis. Harddisk (Storage/Database Size) 40KB to 60KB for each user RAM Database Size Base operating system recommendations (SYSVOL) Third-party applications (Anti-Virus, Monitoring, Backup, ...) Storage/Database Size 40KB to 60KB for each user Network 1 Gb CPU 1000 concurrent users for each core It is recommended to size in cycles, such as through "a three step process [that] will be used as part of the capacity planning cycle." Measure the existing environment, determine where the system bottlenecks currently are, and get environmental basics necessary to plan the amount of capacity needed. Determine the hardware needed according to the criteria outlined in step 1. Monitor and validate that...

Networking - allowing your users access to resources Security - keeping people away from resources Sources: Security Fundamentals: Part 1 at about 6 min. Keywords: Security, Windows Server 2012 R2, Microsoft

Quite moderate minimum requirements for the basic hardware requirements, but depending on usage (as always) the more RAM the better. Processor Minimum: Single processor with 1.4 GHz (x64 processor) or 1.3GHz (Dual Core) Memory Minimum: 512 MB RAM Disk Space Requirements Minimum: 32 GB or greater Usually the question also goes hand-in-hand with the other tasks that machine can perform: "There are certain roles that typically get folded in with the domain controller in all but the biggest networks (e.g. DNS/DHCP/WINS/Cert Server) with little harm." "There are some that get folded into a DC and will cause performance issues on all but the smallest networks (e.g. File Server/intranet server/WDS Server) but these issues are probably manageable depending on load. These previous two classes of role are a case of a balancing act, how concerned you are about performance on your DCs vs. the resources you have available to provision your network. It's b...

Transactional replication typically starts with a snapshot of the publication database objects and data. As soon as the initial snapshot is taken, subsequent data changes and schema modifications made at the Publisher are usually delivered to the Subscriber as they occur (in near real time). The data changes are applied to the Subscriber in the same order and within the same transaction boundaries as they occurred at the Publisher; therefore, within a publication, transactional consistency is guaranteed. Transactional replication is typically used in server-to-server environments and is appropriate in each of the following cases: You want incremental changes to be propagated to Subscribers as they occur. The application requires low latency between the time changes are made at the Publisher and the changes arrive at the Subscriber. The application requires access to intermediate data states. For example, if a row changes five times, transactional replication allows an applic...

Merge replication, like transactional replication, typically starts with a snapshot of the publication database objects and data. Subsequent data changes and schema modifications made at the Publisher and Subscribers are tracked with triggers. The Subscriber synchronizes with the Publisher when connected to the network and exchanges all rows that have changed between the Publisher and Subscriber since the last time synchronization occurred. Merge replication is typically used in server-to-client environments. Merge replication is appropriate in any of the following situations: Multiple Subscribers might update the same data at various times and propagate those changes to the Publisher and to other Subscribers. Subscribers need to receive data, make changes offline, and later synchronize changes with the Publisher and other Subscribers. Each Subscriber requires a different partition of data. Conflicts might occur and, when they do, you need the ability to detect and resolve th...

Although the default option is "Multidimensional and Data Mining Mode" Microsoft actually recommends for new projects "Tabular Mode". According to the Model Features overview Multidimensional supports all features. Microsoft offers a white paper on choosing a Tabular or Multidimensional Modeling Experience in SQL Server 2012 Analysis Services . Tabular Mode Tabular solutions use relational modeling constructs such as tables and relationships for modeling data, and the in-memory analytics engine for storing and calculating data. Because tabular is the newer solution, you might think that migrating an existing multidimensional solution to a tabular format is the correct course of action, but this is usually not the case. Tabular does not supersede multidimensional, and the two formats are not interchangeable. Unless you have a specific reason to do so, do not rebuild an existing multidimensional solution if it is already meeting the needs of your organizatio...

Note: Still needs Microsoft .NET Framework 3.5. Instance Features The configuration and operation of each instance feature of a SQL Server instance is isolated from other SQL Server instances. SQL Server instances can operate side-by-side on the same computer. Database Engine Services Includes the Database Engine, the core service for storing, processing and securing data. The Database Engine provides controlled access and rapid transaction processing and also provides rich support for sustaining high availability. The Database Engine also provides support for the utility control point in the SQL Server Utility. Only Database Engine Services and Analysis Services can be clustered. SQL Server Replication Includes a set of technologies for copying and distributing data and database objects from one database to another and synchronizing between the databases for consistency. You can use replication to distribute data to different locations, and to remote a...

What was it again SQL server setup throws out, when you have your Windows Firewall on?! Rule "Windows Firewall" generated a warning. The Windows Firewall is enabled. Make sure the appropriate ports are open to enable remote access. See the rules documentation at http://go.microsoft.com/fwlink/?LinkId=94001 for information about ports to open for each feature. Keywords: Setup, Firewall, Ports, SQL Server, Microsoft

Data Quality solutions can be divided into the following areas: Cleansing: Amend, remove or enrich data that is incorrect or incomplete. This includes correction, enrichment and standardization. Matching: Identifying, linking or merging related entries without or across sets of data. Profiling: Analysis of the data source to provide insight into the quality of the data and help to identify data quality issues. Monitoring: Tracking and monitoring the state of Quality activites and Quality of Data. Source: Data Quality Basics and Introducing Data Quality Services (DQS) (@13:53) Keywords: Data Quality, Data Quality Services, DQS, SQL Server, Microsoft

Just a word of advice: just because you're on 10.x.y.z does not automatically mean your IT guys really decided for subnet 255.0.0.0 (as class A would suggest). They might have also decided to go for something arbitrary as 255.255.254.0. Important knowledge when you try to configure an NLB'd system and can't figure out why everything seems to work, except when you go outside. Ping fails, telnet fails, ... server not reachable... So, check out the "normal" subnet mask that the machine gets assigned automatically by DHCP change whatever NLB decided itself for the NLB subnet mask add the gateway if it is empty You're good to go... Keywords: Load Balancing, NLB, Windows Server, Redundancy, Failover, Microsoft