DOCSLIB.ORG

Open Database Connectivity Development of the Context Interchange System

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Open Database Connectivity Development of the Context Interchange System Open Database Connectivity Development of the Context Interchange System Andy C.Y. Shum CISL WP# 96-07 December 1996 The Sloan School of Management Massachusetts Institute of Technology Cambridge, MA 02142 Open Database Connectivity Development of the Context Interchange System by Andy C. Y Shum Submitted to the Department of Electrical Engineering and Computer Science December 15, 1996 In Partial Fulfillment of the Requirements for the Degrees of Bachelor of Science in Computer Science and Engineering and Master of Engineering in Electrical Engineering and Computer Science Abstract The Open Database Connectivity (ODBC) development is an extension to the Context Interchange System, a system that aims to provide semantic interoperability between heterogeneous system environments. The development of ODBC is a front end extension which provides users in the Windows working environment the capability to access the Context Interchange System using Windows applications. The primarily goal of the thesis is to present the design and implementation of the ODBC driver which serves as the bridge between the Context Interchange System and ODBC compliant applications. In the mean time, the development of the ODBC driver will serve as a guideline for future integration between common applications and the Context Interchange System. Thesis Supervisor: Michael D. Siegel Thesis Supervisor: Principal Research Scientist, Sloan School of Management Acknowledgments I would like to thank my thesis advisor, Michael Siegel, and Professor Stuart Madnick for giving me the opportunity work in the Context Interchange project. I would like to express my gratefulness to them for their advice and support, especially during my hard time in the project. Thank you so much for having confidence in me and bearing with me! Also, I would like to thank the entire Context Interchange research group for providing such a great working environment. In particular, for Allen Moulton's help and insight in the driver development, Tom Lee's knowledge of the Context Interchange System, Jesse Jacobson's expertise in Excel, and Cheng Goh, Stephane Bressan, Tito Pena, Kofi Fynn and other group members' help and support. Also, I would like to take this opportunity to thank my parents for their support throughout my years at MIT. Thank you so very much for giving me the freedom and opportunity to pursue my career and destiny. Finally, I would like to thank all of my friends at MIT. I could not have make it through without you all! In particular, the "FOPA" member Felix Lo, Oliver Yip and Patrick Chan. Also the Class of 96 members Anita Chan, Jenny Lee and Vinci Leung. In addition, this year's senior Calvin Yuen, Juliap Lee, Preston Li, Zhou Yu, Danny Yim, Chris Leung and Brian Lee. And last but not least, all the juniors, sophomores, and freshmen who know me. Thank you so much for your support. It could have been the worst and dull years of my life without you!. But now, it is definitely one of the most celebrated time of my life. Thank you very much! Contents 1 Introduction 9 2 Background 11 2.1 Context Interchange System Architecture .......................................................... 11 2.1.1 First Tier (Front End)................................................................................ 12 2.1.2 Second Tier (Middleware)...................................................................... 13 2.1.1 Third Tier (Back End).............................................................................. 15 2.2 Open Database Connectivity (ODBC)............................................................... 15 2.2.1 O DBC Defined........................................................................................ 15 2.2.2 Components of ODBC..............................................................................16 2.3 Hypertext Transfer Protocol (HTTP).................................................................17 3 Design of the ODBC Driver 19 3.1 Role of the D river .............................................................................................. 19 3.2 Structure of the Driver ....................................................................................... 20 3.2.1 General Architecture................................................................................ 20 3.2.2 Internal Data Structure.......................................23 3.3 Interactions with the Context Mediator ................................. 26 3.3.1 Comparisons between ODBC API & the Context Mediator Interface.........27 3.3.2 Operations between the ODBC Driver & the Context Mediator.............27 4 Implementation/Scenario 31 4.1 Implemented ODBC Function Calls ................................................................. 31 4.2 Migrating to the Second Prototype .................................... 36 4.3 Algorithms and Tradeoffs .................................... 37 4.3.1 Algorithms Analysis ................................... 37 4.3.2 Tradeoffs ..................................................... o . ......................................... 38 4.4 Scenario of Retrieving Financial Data...............................................................39 4.4.1 Single-datasource query scenario (First & Second Prototypes).............39 4.4.2 Multi-datasource query scenario (Second Prototype)...................45 5 Conclusions 47 5.1 Further ODBC Driver Development..................................................................47 5.2 Re-Design of the Context Mediator Interface................................................... 48 5.3 Full ODBC and Context Interchange System Integration.....................49 5.4 Future Context Interchange System Extensions ................................................ 50 5.4.1 ActiveX .................................................................................................... 50 5.4.2 OLE D B .................................................................................................... 50 5.5 C onclusions....................................................................................................... 51 A Sample HTML formatted result file 52 B ODBC function calls sequence 53 B.1 MS Query Example........................................................................................... 53 B.2 MS Excel Example (query using SQL.REQUEST functions)..................55 C User's Manual 59 C. 1 Guide to create a new Excel spreadsheet using the Context Mediator-ODBC D river ...................................................................................................................... 59 C.2 Complete List of Implemented ODBC API Function Calls...................60 C.3 Specification of the ODBC Driver.....................................................................61 C.4 Miscellaneous Instructions of the Driver ........................................................... 67 List of Figures Figure 2.1-1: The Context Interchange System .......................................................... 11 Figure 2.2-1: ODBC architecture.........................................16 Figure 2.3-1: Examples of HTTP/1.0 protocol.......................................................... 18 Figure 3.1-1: Overview of the ODBC Framework..............................19 Figure 3.2-1: General Structure of the Context Mediator-ODBC Driver...................21 Figure 3.2-2: Internal data structure of the Context Mediator-ODBC driver.............26 Figure 4.1-1: Essential components of the ODBC driver......................................32 Figure 4.3-1: The "pospair" array structure for retrieving data.....................38 Figure 4.4-1: ODBC calls and Context Mediator interface used in MS Query..........41 Figure 4.4-2: Table names are shown after SQLTables is called ............................... 41 Figure 4.4-3: Column names of the chosen table is shown after SQLColumns...........42 Figure 4.4-4: Inputting SQL query in the SQL box..............................42 Figure 4.4-5: Result of the SQL query from the Context Mediator is returned .......... 43 Figure 4.4-6: ODBC function calls and Context Mediator interface for MS Excel........44 Figure 4.4-7: The M S Excel demo......................................................................... 45 Figure 4.4-8: Multi-datasource query example by MS Excel using the second Context Mediator prototype........ ............................ 46 List of Tables Table 2.1-1: Context Mediator interface and its corresponding function[6]...............12 Table 2.1-2 Results of the same query with different specified contexts...................14 Table 3.3-1: ODBC Function Calls and their corresponding Context Mediator Interface ................................................................................................. 28 Table 4.4-1: Summary of the three scenarios given in this section............................ 39 Table C.2-1: Complete list of implemented and non-implemented ODBC function calls ...................................................................................................... 60 Chapter 1 Introduction Over the last few years, the World Wide Web has experienced an exponential growth in its usage. Information of every conceivable kind is being made available on the Web with more being added every day[5]. People can not only view text formatted information from the Internet, but they can also enjoy the power of multimedia through pictures, video and audio clips from the Web. The Internet has indeed become one of the most essential resources for all kinds of information
Load more

Recommended publications
  • Attacker Antics Illustrations of Ingenuity
    ATTACKER ANTICS ILLUSTRATIONS OF INGENUITY Bart Inglot and Vincent Wong FIRST CONFERENCE 2018 2 Bart Inglot ◆ Principal Consultant at Mandiant ◆ Incident Responder ◆ Rock Climber ◆ Globetrotter ▶ From Poland but live in Singapore ▶ Spent 1 year in Brazil and 8 years in the UK ▶ Learning French… poor effort! ◆ Twitter: @bartinglot ©2018 FireEye | Private & Confidential 3 Vincent Wong ◆ Principal Consultant at Mandiant ◆ Incident Responder ◆ Baby Sitter ◆ 3 years in Singapore ◆ Grew up in Australia ©2018 FireEye | Private & Confidential 4 Disclosure Statement “ Case studies and examples are drawn from our experiences and activities working for a variety of customers, and do not represent our work for any one customer or set of customers. In many cases, facts have been changed to obscure the identity of our customers and individuals associated with our customers. ” ©2018 FireEye | Private & Confidential 5 Today’s Tales 1. AV Server Gone Bad 2. Stealing Secrets From An Air-Gapped Network 3. A Backdoor That Uses DNS for C2 4. Hidden Comment That Can Haunt You 5. A Little Known Persistence Technique 6. Securing Corporate Email is Tricky 7. Hiding in Plain Sight 8. Rewriting Import Table 9. Dastardly Diabolical Evil (aka DDE) ©2018 FireEye | Private & Confidential 6 AV SERVER GONE BAD Cobalt Strike, PowerShell & McAfee ePO (1/9) 7 AV Server Gone Bad – Background ◆ Attackers used Cobalt Strike (along with other malware) ◆ Easily recognisable IOCs when recorded by Windows Event Logs ▶ Random service name – also seen with Metasploit ▶ Base64-encoded script, “%COMSPEC%” and “powershell.exe” ▶ Decoding the script yields additional PowerShell script with a base64-encoded GZIP stream that in turn contained a base64-encoded Cobalt Strike “Beacon” payload.
    [Show full text]
  • Microsoft Patches Were Evaluated up to and Including CVE-2020-1587
    Honeywell Commercial Security 2700 Blankenbaker Pkwy, Suite 150 Louisville, KY 40299 Phone: 1-502-297-5700 Phone: 1-800-323-4576 Fax: 1-502-666-7021 https://www.security.honeywell.com The purpose of this document is to identify the patches that have been delivered by Microsoft® which have been tested against Pro-Watch. All the below listed patches have been tested against the current shipping version of Pro-Watch with no adverse effects being observed. Microsoft Patches were evaluated up to and including CVE-2020-1587. Patches not listed below are not applicable to a Pro-Watch system. 2020 – Microsoft® Patches Tested with Pro-Watch CVE-2020-1587 Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability CVE-2020-1584 Windows dnsrslvr.dll Elevation of Privilege Vulnerability CVE-2020-1579 Windows Function Discovery SSDP Provider Elevation of Privilege Vulnerability CVE-2020-1578 Windows Kernel Information Disclosure Vulnerability CVE-2020-1577 DirectWrite Information Disclosure Vulnerability CVE-2020-1570 Scripting Engine Memory Corruption Vulnerability CVE-2020-1569 Microsoft Edge Memory Corruption Vulnerability CVE-2020-1568 Microsoft Edge PDF Remote Code Execution Vulnerability CVE-2020-1567 MSHTML Engine Remote Code Execution Vulnerability CVE-2020-1566 Windows Kernel Elevation of Privilege Vulnerability CVE-2020-1565 Windows Elevation of Privilege Vulnerability CVE-2020-1564 Jet Database Engine Remote Code Execution Vulnerability CVE-2020-1562 Microsoft Graphics Components Remote Code Execution Vulnerability
    [Show full text]
  • Command-Line IP Utilities This Document Lists Windows Command-Line Utilities That You Can Use to Obtain TCP/IP Configuration Information and Test IP Connectivity
    Guide to TCP/IP: IPv6 and IPv4, 5th Edition, ISBN 978-13059-4695-8 Command-Line IP Utilities This document lists Windows command-line utilities that you can use to obtain TCP/IP configuration information and test IP connectivity. Command parameters and uses are listed for the following utilities in Tables 1 through 9: ■ Arp ■ Ipconfig ■ Netsh ■ Netstat ■ Pathping ■ Ping ■ Route ■ Tracert ARP The Arp utility reads and manipulates local ARP tables (data link address-to-IP address tables). Syntax arp -s inet_addr eth_addr [if_addr] arp -d inet_addr [if_addr] arp -a [inet_address] [-N if_addr] [-v] Table 1 ARP command parameters and uses Parameter Description -a or -g Displays current entries in the ARP cache. If inet_addr is specified, the IP and data link address of the specified computer appear. If more than one network interface uses ARP, entries for each ARP table appear. inet_addr Specifies an Internet address. -N if_addr Displays the ARP entries for the network interface specified by if_addr. -v Displays the ARP entries in verbose mode. -d Deletes the host specified by inet_addr. -s Adds the host and associates the Internet address inet_addr with the data link address eth_addr. The physical address is given as six hexadecimal bytes separated by hyphens. The entry is permanent. eth_addr Specifies physical address. if_addr If present, this specifies the Internet address of the interface whose address translation table should be modified. If not present, the first applicable interface will be used. Pyles, Carrell, and Tittel 1 Guide to TCP/IP: IPv6 and IPv4, 5th Edition, ISBN 978-13059-4695-8 IPCONFIG The Ipconfig utility displays and modifies IP address configuration information.
    [Show full text]
  • Winsock Is a Standard Application Programming Interface (API)
    www.installsetupconfig.com An Intro to Windows Socket (Winsock2) Programming & C Language What do we have in this session? Winsock Headers and Libraries Initializing Winsock Error Checking and Handling Addressing a Protocol Addressing IPv4 Internet Addresses Some Note inet_ntoa() Function InetNtop() Function InetPton() Function Byte Ordering Creating a Socket Connection-Oriented Communication Server API Functions Binding, bind() Listening, listen() Accepting Connections, accept() Client API Functions TCP States connect() Data Transmission send() and WSASend() WSASendDisconnect() Out-of-Band Data recv() and WSARecv() WSARecvDisconnect() Stream Protocols Scatter-Gather I/O Breaking the Connection shutdown() closesocket() TCP Receiver/Server With select() Example TCP Sender/client Program Example Testing the TCP Client and Server Programs Testing the TCP Client and Server Programs in Private Network Connectionless Communication Receiver Sender Running Both the UDP Receiver/Server and UDP Sender/Client Testing the UDP Client and select Server Programs in Private Network Message-Based Protocols Releasing Socket Resources 1 www.installsetupconfig.com Miscellaneous APIs getpeername() getsockname() WSADuplicateSocket() Windows CE Conclusion The following figure shows the TCP/IP stack for computer communication. Starting with the Open System Interconnection (OSI) seven layers and the TCP/IP stack. The Winsock is a library used for network communication programming for Windows. 7 Application e.g. HTTP, SMTP, SNMP, FTP, Telnet, SSH and Scp, NFS, RTSP etc. 6 Presentation e.g. XDR, ASN.1, SMB, AFP etc. 5 Session e.g. TLS, SSH, ISO 8327 / CCITT X.225, RPC, NetBIOS, ASP etc. 4 Transport e.g. TCP, UDP, RTP, SCTP, SPX, ATP etc. e.g. IP/IPv6, ICMP, IGMP, X.25, CLNP, ARP, RARP, BGP, OSPF, RIP, IPX, 3 Network DDP etc.
    [Show full text]
  • (CMS) Open Database Connectivity
    Avaya™ Call Management System (CMS) Open Database Connectivity 585-780-701 Issue 1.0 May 2002 COMPAS ID 89705 © 2002, Avaya Inc. All Rights Reserved Notice Trademarks Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information The following trademarks are mentioned in this document: is subject to change. • MultiVantage and DEFINITY are registered trademarks of Avaya Inc. Preventing Toll Fraud • Enterprise, Solaris, SPARCserver, Network Terminal Server, “Toll fraud” is the unauthorized use of your telecommunications system Sun, SunSwift, Solstice, DiskSuite, and Ultra are trademarks by an unauthorized party (for example, a person who is not a corporate or registered trademarks of Sun Microsystems, Inc. employee, agent, subcontractor, or working on your company's behalf). • INFORMIX is a registered trademark of Informix Software, Be aware that there may be a risk of toll fraud associated with your Inc. system and that, if toll fraud occurs, it can result in substantial additional • Multiport is a registered trademark of Aurora Technologies, charges for your telecommunications services. Inc. • Windows is a registered trademark of Microsoft, Inc. Avaya Fraud Intervention All other product names mentioned herein are the trademarks of their If you suspect that you are being victimized by toll fraud and you need respective owners. technical assistance or support, call Technical Service Center Toll Fraud Intervention Hotline at +1 800 643 2353 for the United States and Ordering Information Canada. For additional support telephone numbers, see the Avaya web Call: Avaya Publications Center site: Voice +1 800 457 1235 http://www.avaya.com Fax +1 800 457 1764 Select Support, then select Escalation Lists US and International.
    [Show full text]
  • CEWES MSRC/PET TR/99-15 Using Webhla to Integrate HPC FMS
    CEWES MSRC/PET TR/99-15 Using WebHLA to Integrate HPC FMS Modules with Web/Commodity based Distributed Object Technologies of CORBA, Java, COM and XML by Geoffrey C. Fox Wojtek Furmanski Ganesh Krishnamurthy Hasan T. Ozdemir Zeynep Odcikin Ozdemir Tom A. Pulikal Krishnan Rangarajan Ankur Sood 04h01499 Work funded by the DoD High Performance Computing Modernization Program CEWES Major Shared Resource Center through Programming Environment andTraining (PET) Supported by Contract Number: DAHC94-96-C0002 Nichols Research Corporation Views, opinions and/or findings contained in this report are those of the author(s) and should not be con- strued as an official Department of Defense Position, policy, or decision unless so designated by other official documentation. Using WebHLA to Integrate HPC FMS Modules with Web/Commodity based Distributed Object Technologies of CORBA, Java, COM and XML Geoffrey C. Fox, Ph. D., Wojtek Furmanski, Ph. D., Ganesh Krishnamurthy, Hasan T. Ozdemir, Zeynep Odcikin-Ozdemir, Tom A. Pulikal, Krishnan Rangarajan, Ankur Sood Northeast Parallel Architectures Center, Syracuse University 111 College Place, Syracuse University, Syracuse NY 13244-4100 {gcf, furm, gkrishna, timucin, zeynep, tapulika, krrangar, asood} @ npac.syr.edu Keywords: Interactive Simulation, Military, Personal Computers, Standards ABSTRACT HLA standards for interoperability between various DoD Modeling and Simulation paradigms are being enforced in parallel with the rapid onset of new Object Web / Commodity standards for distributed objects and componentware, emergent at the crossroads of CORBA, COM, Java, and XML technologies. WebHLA explores synergies between and integrates both trends by offering Object Web based implementation of the HLA framework. Our goal is to deliver a uniform platform that facilitates conversion of legacy codes to and development of new codes in compliance with HLA, HPC and Object Web standards.
    [Show full text]
  • A Novel Method to Manage Network Requirements S
    International Journal of Pure and Applied Mathematics Volume 116 No. 13 2017, 9-15 ISSN: 1311-8080 (printed version); ISSN: 1314-3395 (on-line version) url: http://www.ijpam.eu Special Issue ijpam.eu A NOVEL METHOD TO MANAGE NETWORK REQUIREMENTS S.Pothumani 1, Dr.J.Hameed Hussain 2 1Assistant Professor , Dept. of CSE, Bharath University, Chennai, Tamil Nadu, India 2Dean Engineering , Bharath University, Chennai, Tamil Nadu, India [email protected], [email protected] Abstract: The aim of this paper is to fulfill all possible a message to any client connected in the enterprise network requirements of a network administrator regarding his and Search for the given computer in the network. And also network. This also provides an efficient way for the displays all shared folders of a specified computer [1,2]. system administrator to work offsite and who needs to keep intact with his PC and do his work, so that they can 2. Related work share their PC’s with each other. The system administrator working in a multistoried building can use The existing system is a normal Network Management Tool this tool to manage the network by logging into the which can be used only for the domain based network. It server system in the main branch through LAN or has some difficulties. They are Administrator could not internet using the IP address of the server and control his control the network when he is out of station, A Remote- system and network or can work with the others. Based tool is not yet found ,Remote accessing of any server Network scrutinizer is a software tool that helps an is not possible.
    [Show full text]
  • DENICOMP SYSTEMS Winsock RCP/RSH/REXEC for Win32 Copyright ? 2002 Denicomp Systems All Rights Reserved
    DENICOMP SYSTEMS Winsock RCP/RSH/REXEC for Win32 Copyright ? 2002 Denicomp Systems All rights reserved. INTRODUCTION...............................................................................................................................................1 REQUIREMENTS..............................................................................................................................................1 INSTALLATION ................................................................................................................................................1 REMOVING WINSOCK RCP/RSH/REXEC....................................................................................................2 SECURITY.........................................................................................................................................................2 RSH/REXEC AND FIREWALLS...................................................................................................................3 CONFIGURING WINSOCK RCP/RSH/REXEC .............................................................................................4 WINSOCK RSH CONFIGURATION OPTIONS..........................................................................................5 WINSOCK REXEC CONFIGURATION OPTIONS.....................................................................................6 WINSOCK RCP CONFIGURATION OPTIONS..........................................................................................7 CONFIGURATION NOTES ..........................................................................................................................8
    [Show full text]
  • Ingres 10.1 Connectivity Guide
    Ingres 10S Connectivity Guide ING-101-CN-05 This Documentation is for the end user's informational purposes only and may be subject to change or withdrawal by Actian Corporation ("Actian") at any time. This Documentation is the proprietary information of Actian and is protected by the copyright laws of the United States and international treaties. It is not distributed under a GPL license. You may make printed or electronic copies of this Documentation provided that such copies are for your own internal use and all Actian copyright notices and legends are affixed to each reproduced copy. You may publish or distribute this document, in whole or in part, so long as the document remains unchanged and is disseminated with the applicable Actian software. Any such publication or distribution must be in the same manner and medium as that used by Actian, e.g., electronic download via website with the software or on a CD- ROM. Any other use, such as any dissemination of printed copies or use of this documentation, in whole or in part, in another publication, requires the prior written consent from an authorized representative of Actian. To the extent permitted by applicable law, ACTIAN PROVIDES THIS DOCUMENTATION "AS IS" WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL ACTIAN BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USER OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF ACTIAN IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE.
    [Show full text]
  • The Old New Thing: Practical Development Throughout The
    Praise for The Old New Thing “Raymond Chen is the original raconteur of Windows.” —Scott Hanselman, ComputerZen.com “Raymond has been at Microsoft for many years and has seen many nuances of Windows that others could only ever hope to get a glimpse of. With this book, Raymond shares his knowledge, experience, and anecdotal stories, allowing all of us to get a better understanding of the operating system that affects millions of people every day. This book has something for everyone, is a casual read, and I highly recommend it!” —Jeffrey Richter, Author/Consultant, Cofounder of Wintellect “Very interesting read. Raymond tells the inside story of why Windows is the way it is.” —Eric Gunnerson, Program Manager, Microsoft Corporation “Absolutely essential reading for understanding the history of Windows, its intricacies and quirks, and why they came about.” —Matt Pietrek, MSDN Magazine’s Under the Hood Columnist “Raymond Chen has become something of a legend in the software industry, and in this book you’ll discover why. From his high-level reminiscences on the design of the Windows Start button to his low-level discussions of GlobalAlloc that only your inner-geek could love, The Old New Thing is a captivating collection of anecdotes that will help you to truly appreciate the difficulty inherent in designing and writing quality software.” —Stephen Toub, Technical Editor, MSDN Magazine This page intentionally left blank THE OLD NEW THING This page intentionally left blank THE OLD NEW THING Practical Development ThroughoutT the Evolution of Windows Raymond Chen Upper Saddle River, NJ • Boston • Indianapolis • San Francisco New York • Toronto • Montreal • London • Munich • Paris • Madrid Capetown • Sydney • Tokyo • Singapore • Mexico City Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks.
    [Show full text]
  • Performance Tuning Guidelines for Windows Server 2012 R2
    Performance Tuning Guidelines for Windows Server 2012 R2 Copyright information This document is provided "as-is". Information and views expressed in this document, including URL and other Internet website references, may change without notice. Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred. This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes. This document is confidential and proprietary to Microsoft. It is disclosed and can be used only pursuant to a nondisclosure agreement. © 2012 Microsoft. All rights reserved. Internet Explorer, Microsoft, TechNet, Windows, and Excel are trademarks of the Microsoft group of companies. All other trademarks are property of their respective owners. Contents Performance Tuning Guidelines for Windows Server 2012 R2 ...................................................8 Performance Tuning for Server Hardware ................................................................................9 See Also .............................................................................................................................9 Server Hardware Performance Considerations .........................................................................9 See Also ........................................................................................................................... 14
    [Show full text]
  • Mellanox Winof VPI User Manual Rev 5.10
    Mellanox WinOF VPI User Manual Rev 5.10 www.mellanox.com Rev 5.10 NOTE: THIS HARDWARE, SOFTWARE OR TEST SUITE PRODUCT (“PRODUCT(S)”) AND ITS RELATED DOCUMENTATION ARE PROVIDED BY MELLANOX TECHNOLOGIES “AS-IS” WITH ALL FAULTS OF ANY KIND AND SOLELY FOR THE PURPOSE OF AIDING THE CUSTOMER IN TESTING APPLICATIONS THAT USE THE PRODUCTS IN DESIGNATED SOLUTIONS. THE CUSTOMER'S MANUFACTURING TEST ENVIRONMENT HAS NOT MET THE STANDARDS SET BY MELLANOX TECHNOLOGIES TO FULLY QUALIFY THE PRODUCT(S) AND/OR THE SYSTEM USING IT. THEREFORE, MELLANOX TECHNOLOGIES CANNOT AND DOES NOT GUARANTEE OR WARRANT THAT THE PRODUCTS WILL OPERATE WITH THE HIGHEST QUALITY. ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT ARE DISCLAIMED. IN NO EVENT SHALL MELLANOX BE LIABLE TO CUSTOMER OR ANY THIRD PARTIES FOR ANY DIRECT, INDIRECT, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES OF ANY KIND (INCLUDING, BUT NOT LIMITED TO, PAYMENT FOR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY FROM THE USE OF THE PRODUCT(S) AND RELATED DOCUMENTATION EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Mellanox Technologies 350 Oakmead Parkway Suite 100 Sunnyvale, CA 94085 U.S.A. www.mellanox.com Tel: (408) 970-3400 Fax: (408) 970-3403 © Copyright 2015. Mellanox Technologies.
    [Show full text]