zilongwang/ReadingBank huggingface dataset:
Do not design content in a way that is known to cause seizures. Criteria Supporting Feature Remarks and Explanations 2.3.1 Three Flashes or Below Threshold: Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds. Supported Guideline 2.4 Navigable Provide ways to help users navigate, find content, and determine where they are. Criteria Supporting Feature Remarks and Explanations 2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web Not Applicable 2.4.2 Page Titled: Web have titles that describe topic or purpose. Not Applicable 2.4.3 Focus Order: If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability. Supported With Exceptions If a keyboard is used for navigation there are certain scenarios where the order of focus while using the "tab" key is non sequential. For example, on the SQL server connection authentication dialog after an authentication mode is selected, pressing the "tab" key, the focus should move to "Encrypt Connection" and then to "Trust Server Certificate" instead it moves to the "trust Server certificate" first and then to "Encrypt Connection". In other words the order of focus is non-sequential. 2.4.4 Link Purpose (In Context): The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general. Not Applicable
402.2.5 Braille Instructions. Where speech output is required by 402.2, braille instructions for initiating the speech mode of operation shall be provided. Not Applicable 402.3 Volume. ICT that delivers sound, including speech output required by 402.2, shall provide volume control and output amplification conforming to 402.3. Not Applicable 402.3.1 Private Listening. Where ICT provides private listening, it shall provide a mode of operation for controlling the volume. Where ICT delivers output by an audio transducer typically held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided. Not Applicable 402.3.2 Non-private Listening. ICT provides non-private listening, incremental volume control shall be provided with output amplification up to a level of at least 65 dB. A function shall be provided to automatically reset the volume to the default level after every use. Not Applicable 402.4 Characters. At least one mode of characters displayed on the screen shall be in a sans serif font. Where ICT does not provide a screen enlargement feature, characters shall be 3/16 inch (4.8 mm) high minimum based on the uppercase letter “I”. Characters shall contrast with their background with either light characters on a dark background or dark characters on a light background. Not Applicable
11.2.1.34 Labels or instructions Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.34: Labels or instructions: Labels or instructions are provided when content requires user input. Supported 11.2.1.35 Error suggestion Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.35: Error suggestion: If an input error is automatically detected and suggestions for correction are known, then the suggestions are provided to the user, unless it would jeopardize the security or purpose of the content. Supported 11.2.1.36 Error prevention (legal, financial, data) Where ICT is non-web software that provides a user interface, it shall satisfy the Success Criterion in Table 11.36: Error prevention (legal, financial, data): For software that cause legal commitments or financial transactions for the user to occur, that modify or delete user-controllable data in data storage systems, or that submit user test responses, at least one of the following is true: Reversible: Submissions are reversible. Checked: Data entered by the user is checked for input errors and the user is provided an opportunity to correct them. Confirmed: A mechanism is available for reviewing, confirming, and correcting information before finalizing the submission. Supported 11.2.1.37 Parsing Where ICT is non-web software that provides a user interface and that supports access to any assistive technologies, it shall satisfy the Success Criterion in Table 11.37: Parsing: For software that uses markup languages, in such a way that the markup is separately exposed and available to assistive technologies and accessibility features of software or to a user-selectable user elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate Supported
It is used to retrieve, store, delete, insert and update data in/from the database. DML Commands: - extracts data from the database - inserts new data into the database - updates data in the database - deletes data from the database CALL EXPLAIN PLAN LOCK DDL - Data Definition Language (CREATE TABLE) It is used to create and modify the structure of database objects in the database. DDL Commands: CREATE – creates a new database or index. ALTER - alters or changes the database table. DROP - deletes the database table TRUNCATE COMMENT RENAME DCL - Data Control Language It is used to create roles, permissions, control access and referential integrity to the database. DCL Commands: - gives access privileges to users of the database. REVOKE – withdraws access privileges to users of the database. TCL - Transactional Control Language It is used to manage different transactions occurring within a database. TCL Commands: COMMIT - Saves the work done so that the changes or additions are reflected in future. SAVE POINT – allows us to break the sql code in to blocks and then name that blocks as save point. ROLLBACK - restores the database values to original state since the last commit. SET TRANSACTION Pros and Cons of SQL: Pros: Cons: Very flexible Universal (Oracle, Access, Paradox, Microsoft, etc) Relatively Few Commands to Requires Detailed Knowledge of the Structure of the Database Can Provide Misleading Results
customer. The schedule should be able to be condensed by a week or more if the schedule is strictly adhered to. While each team will have their own specific tasks during the course of the engagement, the events highlight the points of common interaction with the consultants over the course of the engagement. It will be the responsibility of the Engagement Manager to verify that the meetings are conducted and that the consultants communicate the ongoing results of their respective discoveries. (The following calendar is typical for a small-sized engagement of up to 25 workloads to be migrated. Refer to the sales and pricing guidelines for more details.) It is the EM’s responsibility to discuss this schedule with the customer and get their agreement. Get in touch with the EM to discuss this timetable (especially considering on-site and off-site times and customer touch points) and make sure the customer agrees with your schedule by the end of the first week. Engagement Schedule Mon Tue Wed Thu Fri Account Team (work starts two weeks prior to Week 1) Account Team completes the Environment Assessment Questionnaire as much as possible and then sends the remaining checklist needs to the customer for completion. On-site Week 1 Customer kickoff meeting Gather key information to complete the inventory activities and the Conditions of Satisfaction document Create the initial engagement schedule Create the Conditions of Satisfaction document Create project Vision and document Prepare customer environment for workload inventory activities Submit engagement schedule, Vision and Scope document, and Conditions of Satisfaction to customer for acceptance End-of-day team meeting On-site Week 2 Customer status meeting Start workload inventory activities Continue workload inventory activities Continue workload inventory activities (if needed) Start categorization and analysis activities (focus on interviews) Start compiling inventory reports Continue categorization and analysis activities (focus on interviews) Create draft version of inventory reports and workload analysis for internal review End-of-day team meeting Off-site Week 3 Customer status meeting conference call Continued work on inventory and migration reports Start creating SQL Server environment in Microsoft Azure Virtual Machines Produce Migration report
How can I transition the Enterprise Edition in the Server + CAL Model to new licensing? Although Enterprise Edition is moving to a core-based licensing metric, EE Server licenses will be available for Microsoft® SQL Server® 2012 through June 30, 2012 to allow customers to complete planned purchases. Starting July 1, 2012, new EE Server licenses will no longer be available on the price list. However, all existing EE Server licenses with Software Assurance (SA) can be upgraded to SQL Server® 2012 and EE Server SA can be maintained to provide access to future software updates. EE Server licenses upgraded to 2012 and beyond will be subject to a 20 core per server maximum. Can I convert my Enterprise server/CAL licenses into core licenses? No. Programmatic transitions of Enterprise Edition servers to cores will not occur. However, an offering to do this may be available through negotiated EAPs. Customers are encouraged to talk to their Microsoft® representative for specific details regarding their deployments. If I license my physical server with Enterprise Edition core licenses, but don’t have SA, do I get unlimited virtualization rights? No. Customers who license all the physical cores with Enterprise Edition, but choose not to have SA, will be able to deploy up to one virtual machine (VM) per each core license. For example, a customer with a 2 processor server with 4 cores each will need 8 core licenses and deploy up to 8 VMs. Microsoft® SQL Server® 2008 R2 vs. SQL Server® 2012 Differences of note are shown in Red Product Highlights Editions Licensing Models Virtualizations Information platform for applications of all Managed, familiar self-service BI tools Support for large-scale data centers and data warehouses Opportunities to build and extend applications in the cloud Integration with the Microsoft® Application Platform Datacenter Enterprise Standard Small Business Workgroup PDW Web Developer Express Compact Standard Server/CAL or Per Processor Enterprise Server/CAL or Per Processor Datacenter Per Processor Standard Processors Run a single VM per license if all physical processors are licensed License individual VM’s based on virtual processors Standard Server + CAL Run a single VM per license (CALs required) Enterprise Processors Run up to 4 VMs per license if all physical processors are licensed License Individual VM’s based on virtual processors Enterprise Server + CAL
Run up to 4 VMs per license (CALs required) Datacenter Run unlimited VMs per license AlwaysOn high availability Blazing-fast performance Optimized for private cloud Enterprise security/compliance Multi-server manageability Rapid data discovery Managed self-service analytics Single BI semantic model Data quality and management Enterprise BI Standard PDW Web (Through SPLA only) Developer Express Compact Standard Server/CAL or Per Core BI Server/CAL Enterprise Per Core Enterprise w/Software Assurance License all cores on physical hardware to run unlimited VMs Standard/BI/Enterprise License a single VM based on virtual cores used OR with Server + CAL licensing For additional information on Microsoft® SQL Server® 2012, go to the SQL Server® website at:
The following provides a summary comparison of the characteristics of multidimensional and tabular models. Feature group Decision criteria Multidimensional/ Tabular Multidimensional modeling Tabular modeling Time to solution / Longer time to solution. Shorter time to solution. Learning curve / Dimensional modeling and MDX language create a steeper learning curve but natively provide more complex capabilities. Relational modeling and Excel-like DAX language create a less steep learning curve but complex capabilities may require sophisticated DAX expressions. Data model Data relationships / One-to-many. Many-to-many. Reference relationships must be explicitly modeled. One-to-many. Many-to-many requires DAX expressions. Modeling table relationships creates reference relationships. Data model Hierarchies / Native support for standard, ragged, and parent-child hierarchies Native support for standard hierarchies. hierarchies require DAX expressions. Data model Additional data modeling features / Perspectives, translations, actions, drillthrough, stored procedures, and write-back. Perspectives and drillthrough. Business logic Calculation language / MDX DAX Business logic Calculations / Native support for common and complex calculations. Native support for common and many complex calculations. Business Aggregation functions / Sum, Count, Min, Max, Distinct Count, None, ByAccount, AverageOfChildren, FirstChild, LastChild, FirstNonEmpty, and LastNonEmpty. Sum, Count, Min, Max, Average, DistinctCount, and various time intelligence functions like FirstDate, LastDate, OpeningBalanceMonth, and ClosingBalanceMonth. Business logic Hierarchy logic / Functions to navigate standard and parent-child hierarchies. DAX functions to navigate parent-child hierarchies, DAX expressions to implement logic in standard dimensions. Hierarchy logic generally more difficult using DAX. Business logic KPIs / Actual, goal, status, and trend with graphical indicators Actual, goal, and status with graphical indicators.
Business Currency conversion / Supports multi-currency conversion using the Business Intelligence Wizard. Implement using DAX expressions. Data access and storage Scale / Extremely large scale (multi-terabyte) Large Scale (Billions of records) Data access and storage Performance / Indexes and preaggregated measure values stored on disk. Dimension data and query results cached in memory. Approximately 3x data compression. In memory column-based data storage. Approximately 10x data compression. Data access and storage Data sources / Relational databases. Relational databases, Excel, Text, OData feeds, Azure Data Market, Analysis Services. Data access and storage language / MDX DAX MDX (In-Memory mode only) Data access and storage Data storage / MOLAP - Dimension, fact, and aggregated data stored on disk. Dimension data and query results cached in memory. ROLAP – Dimension, fact, and aggregated data stored in a relational database. In-Memory - All data cached in memory utilizing column-oriented xVelocity analytics engine DirectQuery – Data stored in SQL Server 2012. Data access and storage Data compression / Typically 3x. Typically 10x.