• Toad Tutorials For Dummies

    Toad Tutorials For Dummies

    Hello, my name is Robert Pound, and I am a Quest technologist. This video covers the installation of Toad for SQL Server. For this video, it is assumed that the trial bits have been downloaded, your key has been received in the welcome email, and you have administrative privileges on the target system.

    • Learn how to communicate with oracle databases using Toad for Oracle. Learn how to create,read,update and delete data. Udemy for Business Get your team access to Udemy’s top 3,000 courses anytime, anywhere. Try Udemy for Business Become an instructor Turn what you know into an opportunity and reach millions around the world.
    • Other trademarks and registered trademarks used in this guide are property of their respective owners. Toad Data Point 3.3. Getting Started Guide.
    • Beginner's Guide to Using Toad. Chapter 1: Getting Started. Chapter 1: Getting Started. Welcome to Toad. Toad for Oracle provides an intuitive and efficient.

    Congratulations on your decision to read this book, Sams Teach Yourself PL/SQL in 21 Days, Second Edition! If you are new to the Oracle environment, this book will help you learn and master Oracle's built-in procedural language quickly. Knowledge of PL/SQL (Procedural Language/Structured Query Language) is becoming a fundamental necessity no matter which of Oracle's many products you use. Today, on your first day of this PL/SQL tutorial, you will accomplish these tasks:. Learn what PL/SQL is and why you should master it.

    Learn what resources you need to finish this book. Write your first PL/SQL function Over the remaining 20 days, you'll delve deeper into the power and capabilities of this language and learn how to leverage its power in your applications regardless of whether you are doing client/server programming with Oracle's tools (such as Developer/2000), using other front-end tools (such as PowerBuilder), or simply writing some batch jobs that run on the server. What Is PL/SQL? PL/SQL is a procedural language that Oracle developed as an extension to standard SQL to provide a way to execute procedural logic on the database. New Term - If you have worked with relational databases in the past, you are no doubt familiar with SQL, which stands for Structured Query Language.

    SQL itself is a powerful declarative language. It is declarative in the sense that you describe the results that you want but not how they are obtained. This is good because you can insulate an application from the specifics of how the data is physically stored. A competent SQL programmer can also push a great deal of processing work back to the server level through the creative use of SQL. There are limits, though, to what you can accomplish with a single declarative query. The real world is seldom as neat and clean as we would like it to be.

    Developers often find themselves needing to execute several queries in succession and process the specific results of one query before going on to the next. This leads to two problems in a client/server environment:. The procedural logic, that is, the definition of the process, resides on client machines. The need to look at the data from one query and use it as the basis for the next query results in an increased amount of network traffic.

    Why are these problems? The procedural logic on client machines can quickly become out of sync if the software is upgraded.

    It can also be implemented incorrectly, resulting in a loss of database integrity. The need to pull down large amounts of intermediate data to a client results in a long wait for the end users who must sit there staring at the hourglass while the data is transferred to their machines. The cumulative effects of a number of clients pulling large amounts of data across the network further decrease performance.

    PL/SQL provides a mechanism for developers to add a procedural component at the server level. It has been enhanced to the point where developers now have access to all the features of a full-featured procedural language at the server level. It also forms the basis for programming in Oracle's continually evolving set of client/server development tools, most notably Developer/2000. Why Learn PL/SQL? If you are developing with Oracle products, Developer/2000 for example, the answer to this question is simple. You need to know PL/SQL because those products use PL/SQL for any procedural code.

    But what if you don't develop with Oracle's products? What if all you use is Oracle's database engine? Is PL/SQL of any use to you? Absolutely it is.

    Regardless of the front-end tool that you are using, you can use PL/SQL to perform processing on the server rather than the client. You can use PL/SQL to encapsulate business rules and other complicated logic. It provides for modularity and abstraction.

    You can use it in database triggers to code complex constraints, which enforce database integrity; to log changes; and to replicate data. PL/SQL can also be used with stored procedures and functions to provide enhanced database security. Finally, it provides you with a level of platform independence.

    Oracle is implemented on many hardware platforms, but PL/SQL is the same on all of them. It makes no difference whether you are running Personal Oracle on a laptop or Oracle8i Enterprise on UNIX. Regardless of what development tools you use, if you are developing in an Oracle environment, your knowledge of PL/SQL and your ability to apply it will give you a competitive advantage against those who do not have that knowledge.

    With PL/SQL you have the power to make your applications more robust, more efficient, and more secure. SQL, SQL.Plus, PL/SQL: What's the Difference? This question has bedeviled many people new to Oracle. There are several products with the letters 'SQL' in the title, and these three, SQL.Plus, SQL, and PL/SQL, are often used together. Because of this, it's easy to become confused as to which product is doing the work and where the work is being done. This section briefly describes each of these three products.

    SQL SQL stands for Structured Query Language. This has become the lingua franca of database access languages. It has been adopted by the International Standards Organization (ISO) and has also been adopted by the American National Standards Institute (ANSI). When you code statements such as SELECT, INSERT, UPDATE, and DELETE, SQL is the language you are using. It is a declarative language and is always executed on the database server.

    Often you will find yourself coding SQL statements in a development tool, such as PowerBuilder or Visual Basic, but at runtime those statements are sent to the server for execution. PL/SQL PL/SQL is Oracle's Procedural Language extension to SQL. It, too, usually runs on the database server, but some Oracle products such as Developer/2000 also contain a PL/SQL engine that resides on the client. Thus, you can run your PL/SQL code on either the client or the server depending on which is more appropriate for the task at hand. Unlike SQL, PL/SQL is procedural, not declarative. This means that your code specifies exactly how things get done.

    As in SQL, however, you need some way to send your PL/SQL code up to the server for execution. PL/SQL also enables you to embed SQL statements within its procedural code. This tight-knit relationship between PL/SQL, SQL, and SQL.Plus is the cause for some of the confusion between the products. Contoh surat undangan pernikahan. SQL.Plus SQL.Plus is an interactive program that allows you to type in and execute SQL statements. It also enables you to type in PL/SQL code and send it to the server to be executed. SQL.Plus is one of the most common front ends used to develop and create stored PL/SQL procedures and functions. What happens when you run SQL.Plus and type in a SQL statement?

    Where does the processing take place? What exactly does SQL.Plus do, and what does the database do?

    If you are in a Windows environment and you have a database server somewhere on the network, the following things happen:. SQL.Plus transmits your SQL query over the network to the database server. SQL.Plus waits for a reply from the database server. The database server executes the query and transmits the results back to SQL.Plus. SQL.Plus displays the query results on your computer screen. Even if you're not running in a networked Windows environment, the same things happen. The only difference might be that the database server and SQL.Plus are running on the same physical machine.

    This would be true, for example, if you were running Personal Oracle on a single PC. PL/SQL is executed in much the same manner. Type a PL/SQL block into SQL.Plus, and it is transmitted to the database server for execution. If there are any SQL statements in the PL/SQL code, they are sent to the server's SQL engine for execution, and the results are returned back to the PL/SQL program.

    The important thing is that SQL.Plus does not execute your SQL queries. SQL.Plus also does not execute your PL/SQL code. SQL.Plus simply serves as your window into the Oracle database, which is where the real action takes place. Figure 1.1 illustrates this relationship. Relationship of SQL.Plus, PL/SQL, and Oracle.

    Several other tools besides SQL.Plus can serve as your window to the database. Server Manager, which has an interface similar to SQL.Plus, is one such tool, although Oracle plans to stop supporting it sometime in the future. If you have Oracle Enterprise Manager installed, you should take a look at SQLPlus Worksheet.

    SQLPlus Worksheet is a GUI tool that is fully compatible with SQL.Plus but is much easier to use. If you are a Developer 2000 programmer, you'll have access to Oracle's Procedure Builder—a tool designed for developing and debugging PL/SQL code. You'll read more about SQLPlus Worksheet and Procedure Builder later in this chapter.

    SQL.Plus is used for most of the examples in this book because of its universal availability to developers. It is perhaps still the most widely used tool to develop, test, and create PL/SQL stored subprograms and SQL queries. Note - In addition to Oracle's tools, several third-party vendors also have tools that can be used to develop PL/SQL code. Some of the major products in this space are. SQL-Programmer by Sylvain Faust Inc. Web address:.

    SQL-Station by Platinum Technology Inc. Web address:. SQL-Navigator by Quest Software.

    Web address:. Tool for Oracle Application Developers (TOAD) by Quest Software.

    Web address: What You Need to Finish This Book In order to try the examples and complete the exercises in this book, you will need access to. An Oracle8i database (the Personal Edition will work). SQL.Plus or SQLPlus worksheet Note - Where possible, the exercises and examples in this book have been designed to run equally well under both Oracle8 and Oracle8i.

    Many, especially those in the first nine days, will even run under Oracle7. However, Oracle8i contains many new features that are not available in previous releases. Days 10, 11, 12, 20, and 21, in particular, are heavily focused on the new 8i features. If you do not currently have access to an Oracle database, there are at least two ways to get your hands on one. For a nominal cost, you can visit Oracle's online store and purchase a 30-day evaluation version of almost any Oracle product, including the database. You can get to the online Oracle Store from Oracle's home page,.

    Another option is to join the Oracle Technology Network (OTN). OTN members can download developer-licensed copies of Oracle's database software at no charge. OTN members also have the option of subscribing to various technology tracks in order to get regular shipments of Oracle software CDs. You can register as an OTN member at no cost. The URL to visit is. You will need these database privileges roles:.

    CREATE PROCEDURE. CREATE SEQUENCE. CREATE SESSION. CREATE TABLE. CREATE TRIGGER.

    CREATE VIEW. CREATE TYPE The following Oracle-supplied packages should be available:.

    DBMSOUTPUT. DBMSSQL. UTLFILE. DBMSPIPE.

    DBMSALERT Your database administrator can help you verify that these packages are available to you. If you are using Oracle8i Personal Edition, you can verify the existence of these packages by logging on as the user SYSTEM and issuing the following query: SELECT objectname FROM dbaobjects WHERE owner="SYS' AND objecttype = 'PACKAGE'; The resulting list will show you all packages in the database owned by the user SYS. The packages named in this chapter should be in that list.

    Of those, the DBMSOUTPUT is the most essential and is used throughout most of the exercises and examples to display results. The other packages are discussed only in specific chapters.

    Caution - I recommend that you do not use a production database and that you create the sample tables in a schema that is not shared with other users. If you are using Personal Oracle on your own PC, you won't have a problem with this. If you are using an employer's facilities, you might want to discuss use of the database with your employer's database administrator, or DBA, as they are often called.

    There is nothing inherently dangerous in any of the exercises or examples, but there is always the risk that a coding mistake, such as an infinite loop, might tie up CPU or I/O resources. It's always good etiquette to minimize the potential impact of your mistakes on other developers and end users. Getting Started with PL/SQL By now you should have a basic understanding of what PL/SQL is and how it relates to other Oracle products. You should have access to an Oracle database environment either at work or at home. During the rest of this chapter, you will learn some of the basics of PL/SQL, and you will write your first Oracle stored function.

    PL/SQL Is Block Structured New Term - PL/SQL is referred to as a block structured language A PL/SQL block is a syntactical unit that might contain program code, variable declarations, error handlers, procedures, functions, and even other PL/SQL blocks. The Syntax for a PL/SQL Block DECLARE variabledeclarations BEGIN programcode EXCEPTION exceptionhandlers END; In this syntax, variabledeclarations are any variables that you might want to define. Cursor definitions and nested PL/SQL procedures and functions are also defined here. Programcode refers to the PL/SQL statements that make up the block. Exceptionhandlers refers to program code that gets triggered in the event of a runtime error or exception. The declaration section of a PL/SQL block is optional, although in practice it is unusual not to have any declarations at all.

    The exception handler portion of a PL/SQL block is also optional, and you won't see much of it until Day 7, 'Procedures, Packages, Errors, and Exceptions.' Note - When you're defining PL/SQL functions, procedures, and triggers, the keyword DECLARE is not used. When defining a function, the function specification, or function header as it is sometimes called, begins the block. Similarly, procedure and trigger specifications begin procedure and trigger blocks. Function, procedure, and trigger blocks are covered in more detail on Day 2, 'Writing Declarations and Blocks.' New Term - Any variable declarations must immediately follow DECLARE and come before BEGIN.

    The BEGIN and END keywords delimit the procedural portion of the block. This is where the code goes. The EXCEPTION keyword signifies the end of the main body of code, and begins the section containing exception handling code. The semicolon at the end of the block, and at the end of each statement, is the PL/SQL statement terminator, and signifies the end of the block.

    Tip - Omitting the semicolon at the end of a block is a common oversight. Leave it off, and you'll get a syntax error. Remember to include it and you will save yourself lots of aggravation.

    Blocks such as the one shown in 'The Syntax for a PL/SQL Block' form the basis for all PL/SQL programming. An Oracle stored procedure consists of one PL/SQL block. An Oracle stored function consists of one PL/SQL block.

    An Oracle database trigger consists of one PL/SQL block. It is not possible to execute PL/SQL code except as part of a block. PL/SQL blocks can be nested. One block can contain another block as in the following example: DECLARE variable declarations go here BEGIN some program code BEGIN code in a nested block EXCEPTION exceptionhandlingcode END; more program code END; Nesting of blocks is often done for error-handling purposes. You will read more about error handling on Day 7. Compiling and Executing a Simple Block Are you ready to try writing your first PL/SQL code? Remember that for this and all other examples in this book, you will be using SQL.Plus to send the PL/SQL code to the Oracle database for execution.

    Begin by running SQL.Plus and connecting to your Oracle database. Your initial SQL.Plus screen should look like the one shown in Figure 1.2.

    Next, type in the following lines of code from Listing 1.1 exactly as shown. Notice the slash at the end. It must be typed in as well, exactly as shown. Relationship of SQL.Plus, PL/SQL, and Oracle.

    Initial SQL.Plus screen. Listing 1.1 Your First PL/SQL Block DECLARE x NUMBER; BEGIN x:= 72600; END; / Tip - The slash at the end tells SQL.Plus that you are done typing PL/SQL code. SQL.Plus will then transmit that code to the Oracle database for execution. The slash has meaning to SQL.Plus only, not to PL/SQL. Tip - The slash character must be typed on a line by itself, and it must be the first character on that line; otherwise, it will get sent to the database and generate an error message. After you type the slash, SQL.Plus transmits your code to Oracle for execution. After your code executes, your output should look like the following: declare x integer; begin x:= 65400; end; / PL/SQL procedure successfully completed The code you just executed was probably not very exciting, possibly because there was no output.

    PL/SQL does have some limited output facilities, and next you will learn how to produce some simple screen output. What About Some Output? When it was originally designed, PL/SQL had no output facilities at all. Remember that PL/SQL is not a standalone language.

    It is almost always used in conjunction with some other program or tool that handles the input, output, and other user interaction. Oracle now includes the DBMSOUTPUT package with PL/SQL, which provides you with some limited output capabilities. You will learn more about packages during Day 8, 'Using SQL,' but for now it's enough to know that you can use the dbmsoutput.putline procedure as shown in Listing 1.2. Listing 1.2 PL/SQL Block Showing the Use of the dbmsoutput.putline Procedure DECLARE x NUMBER; BEGIN x:= 72600; dbmsoutput.putline('The variable X = '); dbmsoutput.putline(x); END; / The dbmsoutput.putline procedure takes exactly one argument and generates a line of text as output from the database server.

    In order for you to see that line of text, you must tell SQL.Plus to display it. This is done with the SQL.Plus command: SQL SET SERVEROUTPUT ON. Type the preceding command now.

    It needs to be executed only once per session, so you won't need to reissue it unless you exit SQL.Plus and get back in again. Next, type in the PL/SQL code from Listing 1.2. The resulting output from SQL.Plus should look like that shown below. The variable x= 72600 Note - It is SQL.Plus that prints the server output on the screen for you to see.

    You must remember to execute the SET SERVEROUTPUT ON command, or you won't see any output. You also can use the SET SERVEROUTPUT OFF command to turn off output when you don't want to see it.

    This thread is for anyone who wants to begin using TuneECU and would like to avoid any potential confusion. It may come easy for some and work flawlessly the first time around, but for others, including myself, you may run into issues that can become major headaches. So, if you want the idiots guide to using TuneECU, these are the steps you should follow: 1. Download The Software: You can download the newest version of TuneECU here: I recommend after you download and unzip the file, you save the application directly to the C drive.

    Also make sure there is a copy of the TuneLibrary.dll to the C drive as well. TuneECU needs this in order to operate and will be part of the download. Download The Drivers: You will need a specific set of FTDI drivers for the cable you will buy, and you can download those here: Make sure you download the correct drivers for whatever operating system you are running. If you are unsure whether you have a 32 or 64 bit OS, you can find this by right clicking on My Computer and viewing properties. Although your cable may come with a driver installation disc, and although Windows can connect to the internet to find suitable drivers automatically, you NEED to use the drivers from the previous link. Anaconda movie star cast.

    Download the drivers, create a folder in your C drive (I named mine 'TuneECU Drivers') and save the driver files to that location. 3.Buying A Cable: I think most will agree with me that the biggest cause for problems with using TuneECU is getting hold of a non compatible cable.

    You may hear others talk about a cheap eBay or Amazon cable they used with success, but you don't necessarily know what you are getting when you buy from these vendors. The only cable I or anyone else will be able to 100% say will work with absolute certainty is this one: Regardless of what anyone tells you, I highly recommend you buy this cable and not have to worry about another one potentially not working. Trust me, its not worth it! Installing Drivers: Once you get the cable, this is how you will install the drivers. First ensure you are not connected to the internet by disconnecting any hardlines you may have and disabling wireless. Then plug in the cable to your laptop. Windows will try to install drivers, but do not allow it to connect to the internet by saying no to that option and clicking 'manually install' drivers.

    Then you will browse files on your computer and point Windows to the folder location where you saved the driver files. On my computer, installation wizard never actually appeared, so I had to do it all manually. Simply go into devices and printers in the control panel, and you will see the USB device plugged in.

    Double click on it to open it. Go to the hardware tab, and then click on properties, and then change settings. Then go to the driver tab, and click update drivers. Again, tell windows you want to manually browse, and point windows to the file location where you saved the drivers.

    Once you do this, you should get a message saying the drivers were updated correctly. You will then get another message saying that windows could not install the drivers. No need to worry, this is windows trying to install driver software for the serial port you are using with the cable. Again, go into devices and printers, click hardware, and now you will see two items, the USB converter which you just updated, and a serial port. Double click on the serial port, and follow the same instructions as above to update the port with the FTDI drivers. While you are doing all this, I also recommend you turn off VCP for the driver as it is unnecessary and could potentially interfere with your ability to connect. With the cable plugged in, go to devices and printers, double click on the USB converter, click on the converter, click on properties, go to the advanced tab, and unclick VCP.

    Finding A Tune: You can find a tune you want for your specific model number (based on vin number) from here: Create a folder in your C drive, I named mine 'TuneECU maps' and save whatever tune you plan on using here. In addition to the tunes from the TuneECU page above, you can share others with friends and forum members. Save all to the same location for ease of use.

    Connecting: To connect to the bike, do the following. First, make sure any antivirus programs on your laptop are disabled and that the lap top is connected to a power source. Also, turn off any screen savers or sleep mode settings, and go into power settings and ensure the screen never dims and the computer never enters sleep mode when its plugged in. Then open up the TuneECU program from where it is saved on the C drive. Turn off the autoconnect feature of TuneECU by clicking on the options download and unclicking autoconnect.

    Then plug in the cable to the same USB port where you had it when you installed the drivers. Pull off the seat on your bike. Plug your bike into the tender.

    Remove the headlight fuse only (# 8 for the speed triple) Then connect the other end of the cable to the OBDII connector. You will have to then have the key to turned to the on position, and the kill switch to the run position, and you should be all set. Do not start the bike.

    In TuneECU click on the ECU dropdown, and then connect. You should see blinking red light in the lower right hand corner which means its initializing. If all is correct, it should then turn yellow and then green as it connects and authenticates. Once connected, your vin number will appear as well as a battery icon which shows voltage.

    At this point, you want to read the OEM map off the bike and save a copy. Click the ECU dropdown, and then read map. This will take some time.

    Watch Insidious: Chapter 3 (2015) Full Movie Online Free - Putlocker - 123movies - gostream Putlockers-Free. After trying to connect with her dead mother, teenager Quinn Brenner, as. Chapter Watch Insidious: Chapter 3 full movie free.A pre-quel set prior to the haunting of the Lambert family members that unveils how talented psychic Elise Rainier unwillingly confirms to use her capability to contact the dead to be able to help a teen girl that has been aimed by a risky paranormal entity.

    For me it took longer than 20 mins and I left my computer which is why you want all screen savers, sleep modes, or screen dimmers shut off. Once it reads successfully, the OEM map will populate the screen. Save a copy of this map by clicking the file dropdown, and save map file.

    You will want to save a copy of this tune to the folder where you have others tunes stored. Once you have saved the OEM map, you can download the new map of your choice. Open up the map you want by clicking the file dropdown, and then open file. Open the map you want from the folder you created. Once it is open, click on the ECU dropdown, and then download. This will begin the download process and if all the above steps were followed, you should be all set! Troubleshooting: If you encounter a failed download, or timed out scenario, there is a good chance it is because you didn't listen to my cable recommendation above and went with something else.

    No worries, now you just need to order the correct Lonelec cable and wait for it to be delivered from England which can take up to 7 business days. In other words, get this one to begin things and avoid any trouble.

    Just know that after a failed download scenario, you will NEED to have a map opened up in the TuneECU program when you go to reconnect to the bike or it will NOT initiate the recovery mode. With the map of your choice open, and the cable connected, try to connect, and then click OK when the recovery option is offered.

    This will recover the ECU, or in other words, download whatever map you have open in the TuneECU screen, onto the bike, and you will be all set! After The Download: Once you download a new map onto the bike, you will have to reset adaptations to get the bike ready to run correctly with the new map. Do this by going into the test pane, and clicking reset adaptions, then ok when prompted. You will get a message on the bottom of the screen saying it was done successfully. Once you do this, then start the bike, and with never applying any throttle, let it idle until the fan kicks on, and then let it go for another 12 mins to complete the 12 minute tune which is when the bike will re adapt to the new maps for idle settings.

    You should see the TPS indicator light turn green again (if you have a Kiehin ECU -ed) which means it has completed the idle adaptation process. Then go out and ride!

    As you ride the bike through the rev ranges and such, it will continue to learn and adapt to the new map. Hope I didn't forget anything, and I tried to keep this user guide as short and to the point as possible. If I can help anyone avoid the troubles that I ran into, it will all be worth it. Not trying to speak for Forchetto, but I expect that he is not alluding to you. Your posts have been sensible. Quite obvious you are not impaired while posting.unlike. Thanks for taking the time to write up and post your guide.

    Very well written. No, I know the type of posts he was referring to. Was just joshing with that comment.

    Poor posting etiquette, or even worse, dumb posts, have always been a pet peeve of mine as well. Thanks for the compliment on the guide. Hopefully it can help others from running into potential issues in the future. May I add the following which I wrote when I accidentally didn't disconnect from the ECU and the bike wouldn't start. It's a real step by step instruction to download a new map to your ECU These instructions were used on a 2010 NJ2 Speed Triple 1050.

    You don't need any tools. Remove your seat and the ECU cable connector is just sitting in front of the fusebox (behind the tank) Start laptop Plug cable into laptop Start TuneECU - select the map view / edit mode Plug cable into bike Pull headlight and tailight fuses (save battery - Keihin ECUs don't like a voltage drop). The 2 fuses are marked on the underside of the fusebox cover. 20amp and 5 amp respectively Turn on ignition (do not start bike) Select Connect from TuneECU menu (it may auto-connect) On the TuneECU menu - Read your map (this backs up your ECU's current map on the bike) File - Open your new map file Select download to the bike - this takes about 1 - 2 minutes When finished - select disconnect from the menu. This is important you do this before turning off the ignition as it 'closes' the program mode on the ECU (mistake I made) After TuneECU disconnects - Turn off the ignition Put fuses back in Wait 10 - 15 seconds Turn on ignition Reconnect with TuneECU Select Reset Adaptation (takes about 30 seconds for the menu item to come selectable as TuneECU connects). Once reset and with Tune ECU still connected - start your bike.

    Make sure you don't touch / twist the throttle - just thumb the starter until she fires (get your grubby hand off the throttle grip ok?:-) Watch the TPS indicator at the bottom left corner of the TuneECU screen. When it goes green (after about 5 - 12 minutes bike has to come to temp etc.) the ECU has baselined the TPS Disconnect ECU on the menu Turn off bike Disconnect computer from bike.

    I would like to thank Ebster for his easy instructions which resulted in a perfect procedure. Two points I would like to add though. Don't forget to replace the headlight fuse before trying to start the bike. I tried for a good five minutes before realising 2. Triumph seem to use map 10466 as standard for the Arrow low boy system which is for 91 RON fuel and resulted on too much popping and farting for my liking.

    I replaced this with the 10465 map, which is a lot better. Also, the dealer originally mapped the bike and got it back out on the parking lot in about 20 minutes, so there's no way they could have waited for the diagnostic stages to complete before giving it back to me.

    Just a word of note for anyone in the future who is letting a dealer do the rap.

    Toad Tutorials For Dummies