Event Location:
Seminole Community College
100 Weldon Boulevard
Orlando, Florida
Abstract:
Learn how to create a web-based reporting dashboard in Reporting Services 2008. This session will show you how to use the 2008 Report Viewer controls inside an ASP.NET page while also demonstrating the use of parameters supplied through the client interface. Examples ASP.NET and C#.
Speaker(s): Darren Herbold,
Abstract:
SQL 2008 introduces a number of new features to help monitor and diagnose problems with SQL Servers. This session will cover the use of Extended Events and the Performance Data Collectors to monitor and troubleshoot common problems with SQL Server, while having a minimal impact on the Server itself.
Speaker(s): Jonathan Kehayias,
Abstract:
In this presentation I would present some of the more arcane aspects of SSRS including advanced charting, using custom code in reports, subreports and navigation internally and externally in Reporting services. I have been a trainer in the past and I've found it best that when I've made presentations my usual rule is to not allow any questions during the presentation, this avoids "presentation hi-jacking" by some attendees. I aim at having at least the last quarter hour for questions. I aim for above all an instructional and entertaining time.
Speaker(s): Neil Marchadie,
Abstract:
This idea delivers a series of SSRS 2008 reports added to the DBA Repository. One is a working Gantt chart for reporting on SQL Server Agent schedules. I like to call this an "overlay" report, like the old days of the overhead projector where transparencies could be combined in chart form to show time-differentiated values or conicidence. This is vital to a DBA so that he or she can see when jobs overlap on all servers that may cause contention for resources. This is ideal for creating the best-fit schedule for existing jobs or answering scheduling decisions with future jobs. The presentation will cover the follow technologies specific to the popular DBA Repository: SSIS (2008), Reporting Services (2008), and new gauge and range style repor
Speaker(s): Rodney Landrum,
Abstract:
MVP Kent Waldrop takes a quick tour of a few of the SQL issues that come up frequently in the MSDN Transact SQL forum. Some of the topics covered include set oriented processing, pitfalls of user defined functions, working with string lists, filtering by date and time and more.
Speaker(s): Kent Waldrop,
Abstract:
Virtualization is a hot topic these days, and SQL Server is often considered for virtualization. This session will cover the various technologies available for virtualizing SQL Server, how to determine whether or not a SQL Server is a canidate for virtualization, as well as alternatives to virtualizing SQL for Disaster Recovery scenarios.
Speaker(s): Jonathan Kehayias,
Abstract:
this session will take a quick overview of how to create a typical user form using InfoPath for deployment in SharePoint so that it displays in the user's web browser. It will also take a look at creating reusable controls for your InfoPath forms and how you can use data from a SharePoint list to display in a browser-based report.
Speaker(s): Michael Antonovich,
Abstract:
Microsoft SQL Server 2008 contains the functionality you need to issue full-text queries against plain character-based data in SQL Server tables. Full-text queries could include words and phrases or multiple forms of a word or phrase.Come learn how to setup your own full text searches in your applications. Give your users search capabilities into their data. It's as easy as 1-2-3! In this session, the attendees will learn not only how to use the standard full text search functionality, but how to customize the built in list of “noise words”, to be able to add and remove words that should or should not be ignored. In addition attendees will also learn how to customize the thesaurus for their own needs. DBAs will also find helpful queries
Speaker(s): Robert Cain,
Abstract:
1. Present upgrading a real Analysis Services 2005 cube to Analysis Services 2008 (not Adenture Works) 2. Show some of the new Analysis Services 2008 features 3. Demonstrate a few performance improvement examples side by side (most likely MDX queries using Mosha's MDX Studio to walk through the details of specific improvements.
Speaker(s): Jen Underwood,
Abstract:
Professionals, and Why You Should Care. SQL Professionals have the opportunity to be in the front lines in the Green and Sustainability effort. "Green and Sustainability" encompasses more than just energy conservation, although on that front the new tools in SQL Server 2008 are huge contributors to the Green effort to reduce bits sent across the pipe. When you add keystroke saving and time saving to the Green and Sustainability effort, SQL Server 2008 can contribute significant metrics to the war on bits (can you say SSIS and SSRS)! Come to this interactive session to brainstorm with other interested people, hear how Green starts with how you do what you do (Be Green); hear about the opportunities associated with green (Build Gr
Speaker(s): Kathy Malone,
Abstract:
This session describes everything you ever wanted to know about physical index structures, as well as how the optimizer chooses indexes for performance. (Join performance in separate session!)
Speaker(s): Jeffrey Garbus,
Abstract:
XML in SQL 2000 wasn't very exciting and it was easy to dismiss it altogether by just relying on developers to handle any XML needed within the application. SQL 2005 changes the game and this session will show you how to use the new XML data type, do basic XML operations on XML data, and showcase the changes to FOR XML that make it so much more useful. This isn't a session to convince you to use XML, but to show you what you can do with XML if you do need to use it!
Speaker(s): Kendal Van Dyke,
Abstract:
This session will show the attendee how easy it is to quickly display your data on a web page with a minimum amount of code. We will cover displaying, editing, deleting and inserting data.
Speaker(s): Chris Rock,
Abstract:
SQL Server 2008 is FAST! This session looks at how the increase in performance in this latest release is reason enough for an upgrade. On the database engine front there are features such as resource governors, filtered indexes, read ahead scan caching, improved parallelism, native data compression support, sparse column support and non-relational data types. Pulling it all together is the new Performance Studio, which is an integrated framework that you can use to collect, analyze, troubleshoot
Speaker(s): Joe Homnick,
Abstract:
This session will focus on common performance problems, considerations, and solutions. Review of methods for isolating long running queries and techniques for writing better SQL. Learn how to use dynamic management views and functions in SQL Server 2005/2008 for query tuning. Finish with explanation of parameter sniffing and different solutions.
Speaker(s): Plamen Ratchev,
Abstract:
In this session, Ryan will be giving some tips on how to better optimize your 2008 SSIS packages. Specifically looking at the data flow task, the demonstration will take a look at how an existing package performs which contains common and not so common mistakes. Then starting with the source, we will take a look on how to improve the performance of the package by editing some of the properties of each component (such as the new and improved lookup in 2008) contained in the data flow.
Speaker(s): Ryan Fonnett,
Abstract:
This session will go through some common approaches and issues associated with representing people and organizations. It will include reviews of some common models (for example, X.500 based models and PIM inspired models such as VCard) and discuss the implications of current dominant scenarios, particularly social applications together with various strategies for representing and integrating this data with a relational database.
Speaker(s): Patrick Thompson,
Abstract:
I will detail my reasoning why a DBA would benefit from learning PowerShell. I will demonstrate how a DBA can use PowerShell in conjunction with SQL, WMI, and SMO to automate repetitive tasks and better manage their workload.
Speaker(s): Ronald Dameron,
Abstract:
This session will look at publishing Excel spreadsheets to the web using SharePoint and Excel Services. It will show how to view the Excel spreadsheet in a web browser and how to publish portions of the spreadsheet in a web part on a standard web page. It will look into creating parameterized views of the data as well as how to use data connections from other data sources such as SQL Server to provide a data source for the worksheet content.
Speaker(s): Michael Antonovich,
Abstract:
This session will show methods to make your reports both easier to create and more flexible. We will cover data driven layouts and formatting. We will see how templates make it easier to have more consistent report formats and how to setup data sources that are more portable. We will review emailing reports and how this can be integrated into your current application.
Speaker(s): Pam Shaw,
Abstract:
Learn how to use SQL Server Profiler to troubleshoot, audit, and tune your SQL Server. Includes creating custom templates, integrating with Performance Monitor data, and creating scripts for creating server-side traces.
 Frustrated with trying to come up with consistent, “meaningful” test data to test your applications? Wish you could unit test your database? Ever forget to make a backup copy of your stored procedure before you made that one line change (that happens to crash the system)? Tired of feeling like you’re not part of the team? We’ll take a look at how Team System can help ease the pain of database development and change management.
Speaker(s): Jim Blizzard,
Abstract:
This session gives an introduction to Reporting Services while focusing on the features that are new in 2008. It will demo the new report designer layout and how to use the Report Builder 2.0. We will also cover the tablix and newly added Dundas visualizations.
Speaker(s): Devin Knight,
Abstract:
In this session we will explore the steps needed to create a user friendly cube. This will cover the analysis process, a very brief overview of the data mart processes and finally the cube itself. Within the cube we will focus on steps that will ensure a better experience for the user.
Speaker(s): Pam Shaw,
Abstract:
Steve Jones will lead a discussion of how to develop a living resume using the Internet. Branding, polish, and presentation are becoming more and more important as each of us increases our online footprint. Drawing from his experience, Steve will talk about a variety of techniques that have helped and hurt IT professionals looking for employment.
Speaker(s): Steve Jones,
Abstract:
The sequel to "understanding single-table index optimization," you will learn all about SQL Server joins, and how they are optimized.
Speaker(s): Jeffrey Garbus,
Abstract:
At some point in every DBA’s career they’ll be probably be asked to work with transactional replication but most DBAs don’t look under the covers once they’re done walking through the setup wizards. In this session we’ll take a deeper look at setting up, monitoring, and calibrating transactional publications plus share some tricks and tips gleaned from years of experience working with high volume, multiple datacenter topologies.
Speaker(s): Kendal Van Dyke,
Abstract:
This session will present new T-SQL enhancements in SQL Server 2008 including MERGE, table valued parameters, new data types (Date and Time related, FILESTREAM, HIERARCHYID), table value constructors, sparse columns, filtered indexes, delighters, and more.
Speaker(s): Plamen Ratchev,
Abstract:
This session will look in depth at some of the more powerful aspects of Integrations Services: Expressions, Package Configurations, and Precedence Constraints. A short tutorial will show the users how to build up a package structure to allow logging to a remote location determined through configurations as well as capturing errors, destroying the error file if no errors are present and emailing a configurable user if any errors are found.
Speaker(s): Eric Wisdahl,
Abstract:
In this presentation, we'll look at ways of securing SQL Server and coding secure means of data access for an organization's sensitive data. This presentation will cover all audiences, from system administrators, to database administrators, to developers. We'll look at features common across SQL Server 2000/2005/2008 as well as some of the newer features and how to use them for SQL Server 2005 and 2008.
Speaker(s): Brian Kelley,
Abstract:
This presentation would be aimed at current users of SQL Server 2005 SSRS focusing on the improvements and differnces in the latest iteration of SSRS. Substantial changes in the BIDS layout would be covered along with the new enhancements in SSRS 2008. I have been a trainer in the past and I've found it best that when I've made presentations my usual rule is to not allow any questions during the presentation, this avoids "presentation hi-jacking" by some attendees. I aim at having at least the last quarter hour for questions. I aim for above all an instructional and entertaining time.
Speaker(s): Neil Marchadie,
Abstract:
This session will present a top 10 (maybe 20) list of queries and tools that DBAs can use daily. The idea is that everything is included on a single 1G or less thumb drive to be portable. From simple T-SQL statements to full blown SSIS packages, the session demonstrate how to interogate, diagnose, report on, and resolve issues that are most prevalent for DBAs: disk space, security, backup locations, database and server documentation and performance. All queries, which are SQL 2000 and 2005 trie
Speaker(s): Rodney Landrum,
Abstract:
Adding test data into your database can be a time-consuming, boring exercise - but you need valid data scenarios, a range of inputs, and the ability to easily generate large volumes of test data rapidly. With Visual Studio 2008 Database Edition ("Data Dude") find out how you can leverage the powerful tools available to fine-tune your test data, and rapidly generate the data you need to fully test your apps!
Speaker(s): Ryan Dorrell,
Abstract:
LINQ (Language Integrated Query) is a powerful new technology built into the Microsoft.NET 3.5 platform that allows developers to query object graphs (including DataSets, XML and SQL Server databases) with a familiar and easy-to-use query syntax right from their application code. Learn how to setup a LINQ project, retrieve strongly-typed object graphs from SQL Server (including child relationships and object dependencies) and bind this data to an ASP.Net webpage, a Windows Form or a Silverlight/WPF application.
Speaker(s): Brandon Kelly,
Abstract:
You may be liable for the data you keep. You will be liable for the data you destroy. We will discuss the brave new world of e-discovery, liability, and effective database and data retention policies. In addition, you will receive practical guidance on protecting yourself and your company from legal liability and your data from theft and inadvertent disclosure.
Speaker(s): Suzanne Meehle,
Abstract:
Intro to SQL Compact and Data Sync services. In this presentation we go over benefits of SQL Compact not only on a mobile device, but as an amazing alternative to locally cached data for occasionally connected devices like laptops. We will also go over Sync Services for SQL Compact.
Speaker(s): Nikita Polyakov,
Abstract:
Nearly every Data Warehouse, Data Mart, or OLAP Cube is challenged by changes over time. How do you report on a store that was in a different territory last year? What do you do when a product changes categories? This session will show you how to design SQL Tables and Analysis Services dimensions that will accurately model changes over time.
Speaker(s): Robert Hatton,
Abstract:
While CTEs and Analytic functions were new features in SS2005, this talk will rather focus on the utility of these features focusing on uses gleaned from the speaker's experience. We will cover performance enhancements, clarity of code, and problems to which the recursive capabilities of WITH can be applied as well as some ways to apply analytic functions to better performance.
Speaker(s): Terry Bomberger,
Abstract:
A presentation on preparing ahead of time for the ultimate loss of data due to hurricanes, floods, fires, theft or even server crashes. This session will cover various options for protecting your databases and the pros cons of each.
Speaker(s): Brandie Tarvin,
Abstract:
A beginner level session on the available types of SQL database backups and how their choices affect your database recovery. This focuses on how to implement backups and how to come to a decision on which backup / recovery policy is best for your workplace. Note: This session is not the same as Disaster Recovery - Preparing for the Storm
Speaker(s): Brandie Tarvin,
Abstract:
We will talk about the different databinding modes and how to validate data. In this demo we will create a wcf service to send data to a silverlight app. We will bind this data to controls and a datagrid
Speaker(s): Kenneth Tucker,
Abstract:
Data Scrambling is aimed to assist DBA-s to represent schema, data volume and characteristics of data without divulging PII and other real data. Data scrambling provides a realistic data environment for demonstration, training or testing purposes. This presentation will give an understanding of the levels, problems and possible solutions of Data Scrambling, together with a practical demonstration.
Speaker(s): Andreas Etelkozi,
Abstract:
Intersested in learning about data warehousing? SQL Server 2008? Come to this session and learn about both. We will specifically look at the new features for data warehousing with SQL Server 2008.
Speaker(s): Wes Dumey,
Abstract:
This is a beginner to intermediate level session that will show you how and why statistics are created, how the impact query plans, how to maintain statistics, and what to do when statistics works against you due to uneven data distribution.
Speaker(s): Andy Warren,
This is a list of speakers from the XML Guidebook records. The details and URLs were valid at the time of the event.
Contact: http://www.campuskoder.net
Nikita has been speaking on SQL Compact and WindowsMobile at code camps. ASP.NET MVP.
Chris Rock is a developer, DBA, and trainer for End to End Training. Chris is a frequent presenter at area Code Camps and has written several articles on SQLServerCentral.com and SQLTeam.com.
LinkedIn: https://www.linkedin.com/in/joehomnick
Contact: http://joeblog.homnick.com/
Joe Homnick is a Microsoft Regional Director since the start of the program over 20 years ago and is a principal owner of Homnick Systems (HSI), a Microsoft Gold Certified Partner located in Boca Raton, Florida. HSI is one of the most established Microsoft Certified Partners in the world, dating back to the beginning of the program in 1993. HSI delivers Microsoft services in the areas of system development and implementation through software consulting, development, training and mentoring.
Contact: http://sharepointmike.wordpress.com
Mike Antonovich is the Asst Director Web Services for OCPS in Orlando, FL where he manages the SharePoint portal team. He is also responsible for multiple .Net custom applications used throughout the district. In June of 2010, he published his 7th book: Office and SharePoint 2010 User's Guide. Mike has been using SQL Server since 1998 and SharePoint since 2007. He recently spoke at the PASS Summit in November 2012 on PowerPivot.
I am an active SQL DBA at a public company in St.Pete, and MCT with considerable experience in the field.
Contact: http://www.pragmaticworks.com/about.htm
Darren Herbold, MCDBA, MCSE is a dedicated consultant who is passionate about delivering business value to his clients. With a Bachelors degree in Management Information Systems from Florida State and 10+ years experience in the information technology industry, he has expertise in Business Intelligence, Database Administration, and .Net Software Development. Darren's main focus is on the SQL Server stack where he delivers training, mentoring, and develops Data Warehouse, ETL, and Reporting
Jonathan Kehayias is a MCITP Database Administrator and Developer, who got started in SQL Server in 2004 as a database developer and report writer in the natural gas industry. After spending two and a half years working in TSQL, in late 2006, he was hired as the SQL Database Administrator for OSI Restaurant Partners, parent company of Outback, Carrabbas, and Bonefish Grill. He has experience in upgrading and consolidating SQL environments, in some cases reducing the number of servers by two-thir
Neil has spent many long years in IT (over 25, but who's counting) starting in the days of Hollerith cards, ask your parents about "Do Not Fold, Spindle or Mutilate". He has worked as a developer at Helmsley-Spear and Maidenform in New York and in Jacksonville worked for CPI/Alltel, Blue Cross, Homeside Lending (now WAMU), Merrill Lynch and ADT. He has worked on all level and "flavors" of IT including Mainframes, Windows and Unix and is currently doing SSRS engineering at Red Rocket Solutions,
Contact: https://sqlandy.com
Andy Warren is a SQL Server consultant and trainer based in Orlando, FL. Focusing on administration, performance tuning, and SQL Server patterns and practices, he’s been a SQL Server MVP since 2008. Andy served two terms on the PASS Board of Directors, was a founding principal in SQLServerCentral, and created both the SQLSaturday and SQLRally event models.
LinkedIn: https://www.linkedin.com/in/ericwisdahl
Eric Wisdahl is a computer engineer working in the database field. He has held multiple roles and positions in e-commerce, marketing and insurance industries. Currently, he is working as a database administrator in a development role for an e-commerce company. Eric Wisdahl does not like writing about himself in the third person. It is kind of creepy.
LinkedIn: http://www.linkedin.com/in/kbriankelley/
Contact: https://truthsolutions.wordpress.com/
Brian Kelley is an author, columnist, Certified Information Systems Auditor (CISA), accredited CISA trainer, and former Microsoft Data Platform (SQL Server) MVP (2009-2016) focusing primarily on SQL Server and Windows security. Brian currently serves as a data architect as well as an independent infrastructure/security architect concentrating on Active Directory, SQL Server, and Windows Server. He has served in a myriad of other positions including senior database administrator, data warehouse architect, web developer, incident response team lead, and project manager. Brian has spoken at 24 Hours of PASS, the Marathon of PASS, IT/Dev Connections, SQLConnections, the SSWUG Virtual Conferences, the Techno Security and Forensics Investigation
Contact: http://blogs.estatic.org/users/avatar.aspx?userid=2102
Mr. Kelly is a technical professional with over 10 years experience in developing and leading teams that write "killer apps". Mr. Kelly owned and operated a private micro-consultancy (estatic.org / BusinessRx) for over 4 years, where he built a technical platform that allowed software developers around the world to create high-impact web applications with ease. In January, 2008 Mr. Kelly re-joined his colleagues at Tribridge. Tribridge's success in the Microsoft consulting industry is represente
LinkedIn: https://www.linkedin.com/profile/view?id=176471amp;trk=nav_responsive_tab_profile
Contact: http://mssqlperformance.blogspot.com/
Jeff has been consulting on and performing technical training for MS SQL Server since 1989, Version 4, on OS/2. Since then, he has worked extensively with each release of the product, specializing in performance and tuning, from concept through legacy system, on systems of all sizes, from small start-up company applications to multi-terabyte data warehouses. In addition to hands-on consulting, he speaks at SQLSaturdays several times/year, has a youtube channel with free training, and has written 20 books on database management systems. His latest book is "Transact SQL the Definitive Guide."
LinkedIn: http://www.linkedin.com/in/arcanecode
Contact: http://arcanecode.com
Robert C. Cain (http://arcanecode.com) is a Microsoft MVP, MCTS Certified in BI, and is the owner of Arcane Training and Consulting, LLC. He is also a course author for Plurasight, author for Red Gate's SImple Talk website, and co-author of 4 books. A popular speaker, Robert has presented at events such as the SQL PASS Summit, TechEd, CodeStock, and numerous SQLSaturdays. Robert has over 25 years experience in the IT industry, working in a variety of fields ranging from manufacturing to telecommunications to nuclear power.
LinkedIn: https://www.linkedin.com/profile/view?id=176471amp;trk=nav_responsive_tab_profile
Contact: http://mssqlperformance.blogspot.com/
Jeff has been consulting on and performing technical training for MS SQL Server since 1989, Version 4, on OS/2. Since then, he has worked extensively with each release of the product, specializing in performance and tuning, from concept through legacy system, on systems of all sizes, from small start-up company applications to multi-terabyte data warehouses. In addition to hands-on consulting, he speaks at SQLSaturdays several times/year, has a youtube channel with free training, and has written 20 books on database management systems. His latest book is "Transact SQL the Definitive Guide."
Database Administrator by day and Author by night Brandie Tarvin sails pirate-populated waters, fights evil robots in disguise and turns kingdoms into chaotic rebellious city-states all while coding ETL processes and protecting real-world data from corruption. If it weren't for her, someone else would have the job and where would be the fun in that? Brandie's first computer experience was with a State-of-the-Art Commodore 64 brought home by her father, who informed her that "computers are NOT toys" and would not let her use it until she learned how to program. In late 2003, she turned her hobbies of programming, MUSHing and assisting friends with generic tech support into a full time career as a database administrator. She's been stuck in the fabulous and bizarre world of professional IT work ever since. Currently, Brandie is a Database Administrator Developer for Allstate Dealer Services in Jacksonville. She has published several articles on SQLServerCentral.com, trains her co-workers in SQL Server, and has previously presented at several SQLSaturday events and JSSUG meetings. She also writes fiction and freelances for Catalyst Game Labs in her spare time.
LinkedIn: https://www.linkedin.com/in/jenunderwood
Contact: http://www.impactanalytix.com/
Jen Underwood, a Senior Director at DataRobot, has held worldwide analytics product management roles at Microsoft and served as a technical lead for system implementation firms. She has over 20 years of experience launching new products and turning around failed projects in enterprise data warehousing, reporting, and advanced analytics. Today she designs product and helps analytics professionals learn how to solve complex problems with machine learning in the emerging citizen data science segment. Jen has a Bachelor of Business Administration – Marketing, Cum Laude from the University of Wisconsin, Milwaukee and a post-graduate certificate in Computer Science – Data Mining from the University of California, San Diego.
Contact: https://www.simple-talk.com/blogs/author/2133-rodney-landrum/
Rodney Landrum has been architecting solutions for SQL Server for over 12 years. He has worked with and written about many SQL Server technologies, including DTS, Integration Services, Analysis Services, and Reporting Services. He has co-authored 4 books on Reporting Services. He is been a regular contributor to SQL Server magazine, sqlservercentral.com and Simple-talk.com. Rodney is also SQL Server MVP
Contact: http://www.vb-tips.com
Ken is the President of the Space Coast .Net User Group and a frequent speaker at Florida Code Camps. Ken is also a Microsoft MVP in Visual Basic.
Pam has been a developer for over 25 years. For the last 20 years she has been developing for software vendors. For the last 5 years she has been actively involved with SQL Server. She has bee the President of the Tampa Bay SQL Server Group for the past year.
Contact: http://www.shuffieldlowman.com/meehle.htm
Suzanne D. Meehle is an attorney with the law Ffirm of ShuffieldLowman in Orlando, Florida. Prior to her legal career, Suzanne worked for over ten years as a SQL Server database administrator and systems engineer for software and heath care IT firms such as International Presence, Interactive Media Corporation, Avio Systems, Shared Medical Systems, Electronic Healthcare Systems, and VeArd Computer Research. Her practice includes both transactional and litigation aspects of intellectual property
Neil has spent many long years in IT (over 25, but who's counting) starting in the days of Hollerith cards, ask your parents about "Do Not Fold, Spindle or Mutilate". He has worked as a developer at Helmsley-Spear and Maidenform in New York and in Jacksonville worked for CPI/Alltel, Blue Cross, Homeside Lending (now WAMU), Merrill Lynch and ADT. He has worked on all level and "flavors" of IT including Mainframes, Windows and Unix and is currently doing SSRS engineering at Red Rocket Solutions,
Contact: https://www.simple-talk.com/blogs/author/2133-rodney-landrum/
Rodney Landrum has been architecting solutions for SQL Server for over 12 years. He has worked with and written about many SQL Server technologies, including DTS, Integration Services, Analysis Services, and Reporting Services. He has co-authored 4 books on Reporting Services. He is been a regular contributor to SQL Server magazine, sqlservercentral.com and Simple-talk.com. Rodney is also SQL Server MVP
Contact: http://www.durableimpact.com
Wes Dumey is a Senior Consultant for Durable Impact Systems, a Florida-based provider of business intelligence solutions. Wes has experience working with many Fortune 500 clients. Wes grew up in Missouri and is a Cheif's fan, even when it's difficult to be one. He enjoys flying airplanes and traveling helping executives solve business issues through the use of business intelligence.
LinkedIn: http://www.linkedin.com/in/kendalvandyke
Contact: http://www.kendalvandyke.com
Kendal is a database strategist, community advocate, public speaker, and blogger. A practiced IT professional with over 15 years of SQL Server experience, Kendal excels at disaster recovery, high availability planning/implementation, amp; debugging/troubleshooting mission critical SQL Server environments. Kendal is a Senior Consultant on the Microsoft Premier Developer Support team and President of MagicPASS (http://magicpass.sqlpass.org), the Orlando, FL based chapter of PASS. Before joining Microsoft, Kendal was a SQL Server/Data Platform MVP from 2011-2016.
Contact: http://pratchev.blogspot.com
Plamen is an SQL Server MVP specializing in relational database applications analysis, implementation, and tuning. His particular interest is in design patterns, performance and optimization. In the past two decades he has worked in different roles as database developer and architect in medium and large scale enterprise applications. He has been involved on projects utilizing DB2 and Oracle, but his main passion is SQL Server, which he started using at version 4.2. Plamen has master's degree in computer science with specialization in algorithms and compliers. He enjoys sharing his experience with user groups and at various conferences.
LinkedIn: http://www.linkedin.com/in/kendalvandyke
Contact: http://www.kendalvandyke.com
Kendal is a database strategist, community advocate, public speaker, and blogger. A practiced IT professional with over 15 years of SQL Server experience, Kendal excels at disaster recovery, high availability planning/implementation, amp; debugging/troubleshooting mission critical SQL Server environments. Kendal is a Senior Consultant on the Microsoft Premier Developer Support team and President of MagicPASS (http://magicpass.sqlpass.org), the Orlando, FL based chapter of PASS. Before joining Microsoft, Kendal was a SQL Server/Data Platform MVP from 2011-2016.
Contact: http://www.standingwaiting.com/Resume/WebResume.htm
http://www.standingwaiting.com/Resume/WebResume.htm
LinkedIn: http://www.linkedin.com/in/rdameron
Contact: http://RonaldDameron.com
Ronald Dameron is The Only DBA at a small software company building planet-scale mobile resource management software. He has over 20 years IT experience on a variety of platforms. His current interests are Azure, PowerShell, SQL Server 2016 and Linux. He was a PASS Summit 2015 Speaker Idol contestant and has spoken at SQLSaturday Tampa, Orlando, South Florida, and the Tampa and Orlando SQL User groups. He has recently earned the Competent Communicator Award from Toastmasters International. He is most active on Twitter as @RonDBA.
Database Administrator by day and Author by night Brandie Tarvin sails pirate-populated waters, fights evil robots in disguise and turns kingdoms into chaotic rebellious city-states all while coding ETL processes and protecting real-world data from corruption. If it weren't for her, someone else would have the job and where would be the fun in that? Brandie's first computer experience was with a State-of-the-Art Commodore 64 brought home by her father, who informed her that "computers are NOT toys" and would not let her use it until she learned how to program. In late 2003, she turned her hobbies of programming, MUSHing and assisting friends with generic tech support into a full time career as a database administrator. She's been stuck in the fabulous and bizarre world of professional IT work ever since. Currently, Brandie is a Database Administrator Developer for Allstate Dealer Services in Jacksonville. She has published several articles on SQLServerCentral.com, trains her co-workers in SQL Server, and has previously presented at several SQLSaturday events and JSSUG meetings. She also writes fiction and freelances for Catalyst Game Labs in her spare time.
LinkedIn: http://www.linkedin.com/in/jackcorbett
Contact: http://www.wisemanorwiseguy.com
JJack Corbett began working with SQL Server, Access, and VB in 1999, when he served an apprenticeship with a good friend who was the software development manager at the local paper mill. He found his niche and has concentrated on SQL Server development and administration since late 2000. He has worked with SQL Server through version 2017 and was a Microsoft Data Plaform MVP from October 2011 to October 2016. Jack is passionate about helping companies architect, design, and develop high performance applications based on the Microsoft Data Platform. He also has a passion for seeing database developers get the core application code (the database) protected under source control. Jack has presented at many user groups and SQLSaturday even
Kathy Malone has used Acces since version 1.0, SharePoint since the 2007 version, and was excited to hear at the SharePoint Conference in 2009 that there were 5 sessions on how the then-pending Access 2010 would integrate with SharePoint 2010. She had the opportunity to visit the Access team in Dec 2009, was active in the Office 2010 CTP/Beta, and continues to be explore how the 2 tools work together.
Contact: http://pratchev.blogspot.com
Plamen is an SQL Server MVP specializing in relational database applications analysis, implementation, and tuning. His particular interest is in design patterns, performance and optimization. In the past two decades he has worked in different roles as database developer and architect in medium and large scale enterprise applications. He has been involved on projects utilizing DB2 and Oracle, but his main passion is SQL Server, which he started using at version 4.2. Plamen has master's degree in computer science with specialization in algorithms and compliers. He enjoys sharing his experience with user groups and at various conferences.
My name is Ryan Fonnett, and I work for an international company as a senior consultant called Sogeti, which is a subsidiary of Capgemini. I have been with the company for a little over a year and a half. The technologies that I have a great deal of experience working with are developing web, windows, and services custom apps using the .NET 1.1 to 3.5 frameworks, SSIS, Oracle (9i to 11g), and SQL Server (2000 to 2008). Currently, I am working with a client on an ETL project that will be extracti
Contact: http://www.agilethought.com
Ryan Dorrell is the CTO of AgileThought, a software development services provider headquartered in Tampa, FL. Ryan has been involved in enterprise software development for over a dozen years with both .NET and J2EE. Passionate about building great software, he is deeply involved in helping clients leverage the power of Microsoft Visual Studio Team System and Team Foundation Server.
I have worked with MS SQL Server going back to version 6.0. Before that I worked with Sybase for about 5 years. I've written thousands of stored procedures, functions and triggers and a few hundred DTS packages. I have about 3000 posts on Microsoft’s SQL Server MSDN forums -- most of these posts related to transact SQL. I received MVP awards in 2008 and 2009. I like snorkeling, swimming, bicycling, ice skating and bringing out the best of people.
Jonathan Kehayias is a MCITP Database Administrator and Developer, who got started in SQL Server in 2004 as a database developer and report writer in the natural gas industry. After spending two and a half years working in TSQL, in late 2006, he was hired as the SQL Database Administrator for OSI Restaurant Partners, parent company of Outback, Carrabbas, and Bonefish Grill. He has experience in upgrading and consolidating SQL environments, in some cases reducing the number of servers by two-thir
Contact: http://sharepointmike.wordpress.com
Mike Antonovich is the Asst Director Web Services for OCPS in Orlando, FL where he manages the SharePoint portal team. He is also responsible for multiple .Net custom applications used throughout the district. In June of 2010, he published his 7th book: Office and SharePoint 2010 User's Guide. Mike has been using SQL Server since 1998 and SharePoint since 2007. He recently spoke at the PASS Summit in November 2012 on PowerPivot.
Contact: http://snowstormlife.com/blogs/bliz
Jim Blizzard is the Developer Technical Specialist for Microsoft in Florida, Alabama, and Mississippi, and is based out of Tampa, Florida. Jim worked previously for Microsoft Consulting Services in the application development space, focusing on web development, and was a Developer Evangelist for Microsoft, spreading the good news of .NET to the masses in the Pacific Northwest.
LinkedIn: https://www.linkedin.com/in/deknight/
Contact: http://devinknightsql.com
Devin Knight a Microsoft Data Platform MVP and the Training Director at Pragmatic Works. He is an author of seven SQL Server and Business Intelligence books and speaks at conferences like PASS Summit, PASS Business Analytics Conference, SQLSaturdays and Code Camps. He is also a contributing member to several PASS Virtual Chapters. Making his home in Jacksonville, FL, Devin is the Vice President of the local Power BI User Group and SQL Server User Group (JSSUG).
LinkedIn: http://www.linkedin.com/in/pshaw1129/
Contact: http://sqlpam.wordpress.com/
Pam Shaw has been in IT for over 30 years. Since 2001, Pam has been working with SQL Server, first 2000, then 2005, 2008, 2008 R2, 2012 and now 2014. Pam currently works as a BI Developer as an independent contractor. Pam is also the Chapter Leader of the Hillsborough SQL Users Group PASS chapter and organizer of SQLSaturday Tampa.
LinkedIn: https://www.linkedin.com/in/rob-hatton-3ab4b845
Contact: http://www.RobertJHatton.com
Rob Hatton is the author of the Business Intelligence Team Handbook. Rob is also a past president of the PASS Business Intelligence User Group here in Tampa. He is a veteran B.I. developer with more than 30 years of database experience and dozens of successful B.I. project deployments.
A long time ago (1982) in a place far away (Summit, NJ), Mr. Bomberger was a Facility Engineer in dire need of a CMMS for a pharmaceutical site. A database consultant was hired, a career change was made, and the rest is history. As a consultant, Mr. Bomberger has worked extensively in a wide range of technologies, roles, business application areas, and industries with a focus on databases. He is currently employed as an Architect by Tallan, Inc.
LinkedIn: http://www.linkedin.com/in/way0utwest
Contact: http://www.voiceofthedba.com/
Steve Jones is a Microsoft SQL Server MVP and has been working with SQL Server since version 4.2 on OS/2. After working as a DBA and developer for a variety of companies, Steve co-founded the community website SQLServerCentral.com in 2001. Since 2004, Steve has been the full-time editor of the site, ensuring it continues to be a great resource for SQL Server professionals. Over the last decade, Steve has written hundreds of articles about SQL Server for SQLServerCentral.com, SQL Server Standard magazine, SQL Server Magazine, and Database Journal.
The following is a list of sponsors that helped fund the event.


Matthew Compton
Currently, I'm an Engineering Manager.
Github
Email
Copyright © 2013-2023 by Matthew Compton


Orchestrator release 1.2.7-beta now supports semi-automatic slave promotion to master upon master death, via Pseudo GTID.
When the master is dead, orchestrator automatically picks the most up-to-date slaves and marks them as “Master candidates”. It allows a /api/make-master call on such a slave (S), in which case it uses Pseudo GTID to enslave its siblings, and set S as read-only = 0. All we need to do is click the “Make master” button.
And not for long!
The Call for Papers for Percona Live MySQL Conference and Expo, to be held at Santa Clara in April 2015, is open. The dead line for submissions is Nov. 16th; that’s just around the corner.
As with previous years, we will hold a 4 day conference, the first being a tutorials day and three days for sessions, BoF and lightning talks, as well as community events. The committee is expecting to review at about 250-300 submissions, out of which it will pick at about 100 talks to schedule or reserve.
We will be using these tracks:
- High Availability
- DevOps
- Programming
- Performance Optimization
- Replication and Backup
- MySQL in the Cloud
- MySQL and NoSQL
- MySQL Case Studies
- Security
- What’s New in MySQL
This year we will roughly pre-define the desired number of sessions we wish to have per track. This is not set in stone and everything is fluid. Yet, this will give us better guidelines at choosing and pursuing content for this conference.
Submitting a proposal
We encourage all members of the community to submit their tutorial/session/BoF proposals as soon as possible. Please register/login at the conference home page.
The guidelines for submitting a proposal are generally unchanged; please review past recommendations: [1], [2], [3], [4]. To add to all these:
- Do note that we are likely to only review a proposal just once. Please submit only after you have finalized your draft.
- Make a reasonable length of proposal. We believe 250 - 300 words are quite enough for a good proposal. Please don’t write an essay, and remember that you proposal is what gets printed on the schedule, and what is read by the conference attendees when choosing the next talk to go to.
- Write a descent Bio.
Orchestrator 1.2.1-beta supports Pseudo GTID (read announcement): a means to refactor the replication topology and connect slaves even without direct relationship; even across failed servers. This post illustrates two such scenarios and shows the visual way of mathcing/re-synching slaves.
Of course, orchestrator is not just a GUI tool; anything done with drag-and-drop is also done via web API (in fact, the drag-and-drop invoke the web API) as well as via command line. I’m mentioning this as this is the grounds for failover automation planned for the future.
Scenario 1: the master unexpectedly dies
The master crashes and cannot be contacted. All slaves are stopped as effect, but each in a different position. Some managed to salvage relay logs just before the master dies, some didn’t. In our scenario, all three slaves are at least caught up with the relay log (that is, whatever they managed to pull through the network, they already managed to execute). So they’re otherwise sitting idle waiting for something to happen. Well, something’s about to happen.
Note the green “Safe mode” button to the right. This means operation is through calculation of binary log files & positions with relation to one’s master. But the master is now dead, so let’s switch to adventurous mode; in this mode we can drag and drop slaves onto instances normally forbidden. At this stage the web interface allows us to drop a slave onto its sibling or any of its ancestors (including its very own parent, which is a means of reconnecting a slave with its parent). Anyhow:
We notice that orchestrator is already kind enough to say which slave is best candidate to be the new master (<IP_ADDRESS>:22990): this is the slave (or one of the slaves) with most up-to-date data. So we choose to take another server and make it a slave of <IP_ADDRESS>:22990:
orchestrator 1.2.1 BETA is released. This version supports Pseudo GTID, and provides one with powerful refactoring of one’s replication topologies, even across failed instances.
Depicted: moving a slave up the topology even though its local master is inaccessible
Enabling Pseudo-GTID
You will need to:
- Inject a periodic unique entry onto your binary logs
- Configure orchestrator to recognize said entry.
Pseudo GTID injection example
We will use the event scheduler (must be enabled) to inject an entry every 10 seconds, recognized both in statement-based and row-based replication.
create database if not exists meta;
drop event if exists meta.create_pseudo_gtid_view_event;
delimiter ;;
create event if not exists
meta.create_pseudo_gtid_view_event
on schedule every 10 second starts current_timestamp
on completion preserve
enable
do
begin
set @pseudo_gtid := uuid();
set @_create_statement := concat(‘create or replace view meta.pseudo_gtid_view as select
Make sure to enable event_scheduler in your my.cnf config file.
An entry in the binary logs would look like this:
This post describes in detail the method of using Pseudo GTID to achieve unplanned replication topology changes, i.e. connecting two arbitrary slaves, or recovering from a master failure even as all its slaves are hanging in different positions.
Please read Pseudo GTID and Pseudo GTID, RBR as introduction.
Consider the following case: the master dies unexpectedly, and its three slaves are all hanging, not necessarily at same binary log file/position (network broke down while some slaves managed to salvage more entries into their relay logs than others)
(Did you notice the “Candidate for master” message? To be discussed shortly)
GTID
With GTID each transaction (and entry in the binary log) is associated with a unique mark – the Global Transaction ID. Just pick the slave with the most advanced GTID to be the next master, and just CHANGE MASTER TO MASTER_HOST=‘chosen_slave’ on the other slaves, and everything magically works. A slave knows which GTID it has already processed, and can look that entry on its master’s binary logs, resuming replication on the one that follows.
How does that work? The master’s binary logs are searched for that GTID entry. I’m not sure how brute-force this is, since I’m aware of a subtlety which requires brute-force scan of all binary logs; I don’t actually know if it’s always like that.
Pseudo GTID
We can mimick that above, but our solution can’t be as fine grained. With the injection of Pseudo GTID we mark the binary log for unique entries. But instead of having a unique identifier for every entry, we have a unique identifier for every second, 10 seconds, or what have you, with otherwise normal, non-unique entries in between our Pseudo GTID entries.
Recognizing which slave is more up to date
Given two slaves, which is more up to date?
- If both replicate(d) from same master, a SHOW SLAVE STATUS comparison answers (safe method: wait till SQL thread catches up with broken IO thread, compare relay_master_log_file, exec_master_log_pos on both machines). This is the method by which the above “Candidate for master” message is produced.
- If one is/was descendent of the other, then obviously it is less advanced or equals its ancestor.
- Otherwise we’re unsure - still solvable via bi-directional trial & error, as explained later on.
For now, let’s assume we know which slave is more up to date (has received and executed more relay logs). Let’s call it S1, whereas the less up-to-date will be S2. This will make our discussion simpler.
This post continues Pseudo GTID, in a series of posts describing an alternative to using MySQL GTIDs.
The solution offered in the last post does not work too well for row based replication. The binary log entries for the INSERT statement look like this:
# at 1020
at 1074
#141020 12:36:21 server id 1 end_log_pos 1074 Table_map: test
.pseudo_gtid
mapped to number 33
#141020 12:36:21 server id 1 end_log_pos 1196 Update_rows: table id 33 flags: STMT_END_F
BINLOG ‘
lddEVBMBAAAANgAAADIEAAAAACEAAAAAAAEABHRlc3QAC3BzZXVkb19ndGlkAAMDBw8CQAAE
lddEVBgBAAAAegAAAKwEAAAAACEAAAAAAAEAA///+AEAAACL10RUJDg2ZmRhMDk1LTU4M2MtMTFl
NC05NzYyLTNjOTcwZWEzMWVhOPgBAAAAlddEVCQ4Y2YzOWMyYy01ODNjLTExZTQtOTc2Mi0zYzk3
MGVhMzFlYTg=
‘/!/;
Where’s our unique value? Encoded within something that cannot be trusted to be unique. Issuing mysqlbinlog –verbose helps out:
BEGIN
/!/;
at 183
at 237
#141020 12:35:51 server id 1 end_log_pos 237 Table_map: test
.pseudo_gtid
mapped to number 33
#141020 12:35:51 server id 1 end_log_pos 359 Update_rows: table id 33 flags: STMT_END_F
BINLOG ‘
d9dEVBMBAAAANgAAAO0AAAAAACEAAAAAAAEABHRlc3QAC3BzZXVkb19ndGlkAAMDBw8CQAAE
d9dEVBgBAAAAegAAAGcBAAAAACEAAAAAAAEAA///+AEAAABt10RUJDc1MWJkYzEwLTU4M2MtMTFl
NC05NzYyLTNjOTcwZWEzMWVhOPgBAAAAd9dEVCQ3YjExZDQzYy01ODNjLTExZTQtOTc2Mi0zYzk3
MGVhMzFlYTg=
‘/!/;
UPDATE test
.pseudo_gtid
WHERE
### @1=1
### @2=1413797741
### @3=‘751bdc10-583c-11e4-9762-3c970ea31ea8’
SET
### @1=1
### @2=1413797751
### @3=‘7b11d43c-583c-11e4-9762-3c970ea31ea8’
and that’s something we can work with. However, I like to do stuff from within MySQL, and rely as little as possible on external tools. How do the binary log entries look via SHOW BINLOG EVENTS? Not good.
master [localhost] {msandbox} (test) > show binlog events in ‘mysql-bin.000058’ limit 20;
+——————+——+————-+———–+————-+—————————————+
| Log_name | Pos | Event_type | Server_id | End_log_pos | Info |
+——————+——+————-+———–+————-+—————————————+
| mysql-bin.000058 | 4 | Format_desc | 1 | 107 | Server ver: 5.5.32-log, Binlog ver: 4 |
| mysql-bin.000058 | 107 | Query | 1 | 183 | BEGIN |
| mysql-bin.000058 | 183 | Table_map | 1 | 237 | table_id: 33 (test.pseudo_gtid) |
| mysql-bin.000058 | 237 | Update_rows | 1 | 359 | table_id: 33 flags: STMT_END_F |
| mysql-bin.000058 | 359 | Xid | 1 | 386 | COMMIT /* xid=5460 / |
| mysql-bin.000058 | 386 | Query | 1 | 462 | BEGIN |
| mysql-bin.000058 | 462 | Table_map | 1 | 516 | table_id: 33 (test.pseudo_gtid) |
| mysql-bin.000058 | 516 | Update_rows | 1 | 638 | table_id: 33 flags: STMT_END_F |
| mysql-bin.000058 | 638 | Xid | 1 | 665 | COMMIT / xid=5471 / |
| mysql-bin.000058 | 665 | Query | 1 | 741 | BEGIN |
| mysql-bin.000058 | 741 | Table_map | 1 | 795 | table_id: 33 (test.pseudo_gtid) |
| mysql-bin.000058 | 795 | Update_rows | 1 | 917 | table_id: 33 flags: STMT_END_F |
| mysql-bin.000058 | 917 | Xid | 1 | 944 | COMMIT / xid=5474 / |
| mysql-bin.000058 | 944 | Query | 1 | 1020 | BEGIN |
| mysql-bin.000058 | 1020 | Table_map | 1 | 1074 | table_id: 33 (test.pseudo_gtid) |
| mysql-bin.000058 | 1074 | Update_rows | 1 | 1196 | table_id: 33 flags: STMT_END_F |
| mysql-bin.000058 | 1196 | Xid | 1 | 1223 | COMMIT / xid=5476 */ |
| mysql-bin.000058 | 1223 | Query | 1 | 1299 | BEGIN |
| mysql-bin.000058 | 1299 | Table_map | 1 | 1353 | table_id: 33 (test.pseudo_gtid) |
| mysql-bin.000058 | 1353 | Update_rows | 1 | 1475 | table_id: 33 flags: STMT_END_F |
+——————+——+————-+———–+————-+—————————————+
The representation of row-format entries in the SHOW BINLOG EVENTS output is really poor. Why, there’s nothing to tell me at all about what’s been done, except that this is some operation on test.pseudo_gtid. Obviously I cannot find anything unique over here.
Not all is lost. How about DDL statements? Those are still written in SBR format (there’s no rows to log upon creating a table). A solution could be somehow manipulating a unique value in a DDL statement. There could be various such solutions, and I chose to use a CREATE VIEW statement, dynamically composed of a UUID():
Pseudo GTID is a method to implement a GTID-like solution where slaves are easily connected to one another. This blog post and the following ones will describe work in progress (some 80% completed), where simulation of GTID makes for a good enough basis for refactoring replication topologies. I’m coding this in orchestrator, which already provides a substantial infrastructure support for this.
The final goal: orchestrator will allow you to move a slave below another, using only the data available by those two slaves. The usage is obvious:
- Easy master failover (master dead? Orchestrator will choose the most advanced slave to promote and make it master of its siblings)
- Slave promotion in complex topologies (with deep nested topologies, be able to move a slave up the hierarchy even if its local master is corrupted).
This can all happen with your normal, non GTID, MySQL replication, using your normal binary log files & positions.
This work in progress is inspired by Sam Lambert at GitHub, who has worked on a similar solution with different implementation. I also recall discussions with other DBAs having similar solution.
Pseudo GTID
First thing’s first, the basis for proposed solution is a pseudo-GTID. A unique entry in the binary logs (not necessarily sequential; not necessarily in ascending order). While in GTID implementations we have a unique identifier for each entry in the binary log, with pseudo-GTID we accept an occasional (or frequent) unique entry in the binary log.
There are many ways to do so. Certainly a client can generate a unique Id and invoke some statement on MySQL involving that ID. That would serve as valid grounds for the proposed solution. But I like things to be contained within MySQL. Consider, for example, the following event, which would be my preferred choice in Statement Based Replication (for RBR solution, see next post):
drop table if exists test.pseudo_gtid;
create table if not exists test.pseudo_gtid (
id int unsigned not null primary key,
ts timestamp,
gtid varchar(64) charset ascii
);
drop event if exists test.update_pseudo_gtid_event;
delimiter ;;
create event if not exists
test.update_pseudo_gtid_event
on schedule every 10 second starts current_timestamp
on completion preserve
enable
do
begin
set @pseudo_gtid := uuid();
insert into test.pseudo_gtid (id, ts, gtid) values (1, NOW(), @pseudo_gtid) on duplicate key update ts=NOW(), gtid=VALUES(gtid);
end
;;
delimiter ;
The above is based on Making UUID() and RAND() replication safe. What do we get? Once in 10 seconds (or what have you), a unique entry is written to the binary log.
MySQL’s UUID() and RAND() functions both provide with (pseudo) indeterministic result. UUID()’s result is moreover bound to the host on which it executes. For this reason, both are unsafe to replicate with STATEMENT binlog format. As an example, consider:
master> create table test.uuid_test (id int, u varchar(64));
master> insert into test.uuid_test values (1, UUID());
Query OK, 1 row affected, 1 warning (0.03 sec)
master> select * from test.uuid_test;
+——+————————————–+
| id | u |
+——+————————————–+
| 1 | 7e3596d8-56ac-11e4-b284-3c970ea31ea8 |
+——+————————————–+
The warning we got on the insert directly relates to the following inconsistency on a slave:
slave1> select * from test.uuid_test;
+——+————————————–+
| id | u |
+——+————————————–+
| 1 | 7e379d63-56ac-11e4-8477-3c970ea31ea8 |
+——+————————————–+
The data on the slave is clearly inconsistent with the master’s. The slave, replicating via STATEMENT binlog format, re-executes the INSERT command and gets a different UUID value.
External
One solution to the above is to generate the UUID value from your application. By the time MySQL gets the INSERT statement, the UUID value is a constant string, as far as MySQL is concerned.
Internal
However there’s a way to do it from within MySQL, by decoupling the UUID() function from the INSERT statement. It takes a session variable. Consider:
Outbrain’s orchestrator 1.1.18 is released:
- Support for orchestrator-agent (see announcement): agent pages, support for agent actions, initiation of seeds (provisioning of new/corrupted servers), auditing of seeds.
- Clusters dashboard
- Support for long query auditing
- SSL
- Proxy authentication (e.g. apache2 serving as reverse-proxy with LDAP)
- User control
- Better slave moving rules.
Quick links:
orchestrator now allows for seeding/provisioning of servers via orchestrator-agent. It communicates with agents executing on the MySQL hosts and coordinate transfer of data between them. orchestrator now supports invocation and auditing of seeding operations, and protects you from breaking your seeds. The orchestrator-agent is a solution to Outbrain’s specific use case, and may not appeal to the greater crowd. Nonetheless it is extendible and is released as open source.
orchestrator-agent is a side-kick, complementary project of orchestrator, implementing a daemon service on one’s MySQL hosts which communicates with and accepts commands from orchestrator, built with the original purpose of providing an automated solution for provisioning new or corrupted slaves.
It was built by Outbrain, with Outbrain’s specific use case in mind. While we release it as open source, only a small part of its functionality will appeal to the public (this is why it’s not strictly part of the orchestrator project, which is a general purpose, wide-audience solution). Nevertheless, it is a simple implementation of a daemon, such that can be easily extended by the community. The project is open for pull-requests!
A quick breakdown of orchestrator-agent is as follows:
- Executes as a daemon on linux hosts
- Interacts and invokes OS commands (via bash)
- Does not directly interact with a MySQL server running on that host (does not connect via mysql credentials)
- Expects a single MySQL service on host
- Can control the MySQL service (e.g. stop, start)
- Is familiar with LVM layer on host
- Can take LVM snapshots, mount snapshots, remove snapshots
- Is familiar with the MySQL data directory, disk usage, file system
- Can send snapshot data from a mounted snapshot on a running MySQL host
- Can prepare data directory and receive snapshot data from another host
- Recognizes local/remote datacenters
- Controlled by orchestrator, two orchestrator-agents implement an automated and audited solution for seeding a new/corrupted MySQL host based on a running server.


Charmed's Past is the Present in New Promo
by Sam StoneThe latest episode of The CW's Charmed reboot takes things back to the past in a new promo for Season 2's seventh episode.
The promo for "Past Is Present" sees the sisters and Harry stumble across several women in a compromising position before learning that the Shadow Demon Parker is poised to make a return.
The episode will also see Macy and Harry, a Whitelighter and guide for witches, make a startling discovery as the two grow closer together. Meanwhile, Abby, the latest witch to join the sisters this season, faces a surprising foe with Maggie while Mel embarks on a mission to rescue Kat from certain peril.
Season 2 of Charmed has had the sisters learn more about dark forces actively hunting them when the young witch Abby arrives in town under pursuit by powerful enemies. As the sisters continue to acclimate to their new, magical abilities, they may be facing a familiar foe that threatens the Power of Three and their family legacy.
Charmed, starring Madeleine Mantock, Melonie Diaz, Sarah Jeffery, Rupert Evans, Valerie Cruz, Ser’Darius Blain and Ellen Tamaki, airs Fridays at 8 p.m. ET/PT on The CW.
https://schema.orgBreadcrumbListListItem1Homehttps://www.cbr.com/ListItem2TVhttps://www.cbr.com/category/tv/ListItem3TV Newshttps://www.cbr.com/category/tv/news-tv/ListItem4Charmed's Past is the Present in New Promohttps://www.cbr.com/charmed-past-present-promo/


How white Americans see their relationship with the government
Select a question from the General Social Survey
Confidence in executive branch of federal government
Satisfaction with financial situation
Change in financial situation
How much say about what government does
Don't have any say about what the government does
Government does not care much what people like or think
Number of immigrants to America should be
Immigrants take jobs away


| 009:093 Khan | : |
The ground (of complaint) is only against those who are rich, and yet ask exemption. They are content to be with (the women) who sit behind (at home) and Allah has sealed up their hearts (from all kinds of goodness and right guidance) so that they know not (what they are losing). |
| 009:093 Maulana | : |
The way (to blame) is only against those who ask permission of thee, though they are rich. They have chosen to be with those who remained behind; and Allah has sealed their hearts, so they know not. |
| 009:093 Pickthal | : |
The road (of blame) is only against those who ask for leave of thee (to stay at home) when they are rich. They are content to be with the useless. Allah hath sealed their hearts so that they know not. |
| 009:093 Rashad | : |
The blame is on those who ask your permission to stay behind, even though they have no excuse. They have chosen to be with the sedentary. Consequently, GOD has sealed their hearts, and thus, they do not attain any knowledge. |
| 009:093 Sarwar | : |
The blameworthy ones are those who ask for exemption despite their ability and who preferred to stay at home with those who are truly exempt. God has placed a seal on their hearts but they do not know. |
| 009:093 Shakir | : |
The way (to blame) is only against those who ask permission of you though they are rich; they have chosen to be with those who remained behind, and Allah has set a seal upon their hearts so they do not know. |
| 009:093 Sherali | : |
The cause of reproach is only against those who ask leave of thee, while they are rich. They are content to be with the womenfolk who remain behind at home. And ALLAH has set a seal upon their hearts so that they know not. |
| 009:093 Yusufali | : |
The ground (of complaint) is against such as claim exemption while they are rich. They prefer to stay with the (women) who remain behind: Allah hath sealed their hearts; so they know not (What they miss). |
Concepts/Themes Covered: الجهاد > الجهاد في سبيل الإسلام > أشرار الجند Jihad> The Call to Jihad>The Wicked Soldiers الجهاد > الجهاد في سبيل الإسلام > ذم المتخاذلين عن الجهاد Jihad> The Call to Jihad>Dispraise the Reluctant for the Holy War الجهاد > الغزوات > غزوة تبوك Jihad> The Holy Battles> Tabuk Battle العلاقات القضائية > أحكام قانونية > العفو > الترخيص Judicial Relationships>Legal Rules>Forgiveness>Allowance
This tool uses eight English parallel translations for the Holy Quran imported from Mr. Clay Smith. You can also visit Qurany Concepts for browsing the Quran themes or topics. If you want to search the Holy Quran for keywords, please visit Qurany Keywords.


{% raw %}
The official URL for this profile is:
https://paciowg.github.io/functional-status-ig//StructureDefinition/pacio-fs
An exchange of functional status data for a patient.
This profile builds on Observation.
This profile was published on Wed Feb 24 09:36:30 EST 2021 as a active by HL7 Patient Care Work Group.
{% endraw %}


We are "event savers"! Our job is to ensure that your event is a success, any day, any time all year round. At Everserved, your problem is our problem. We make your events happen according to your desired taste. Our commitment to our Customers is our primary focus. Our joy lies in ensuring that your event holds without any hitches.
Blessing Okere is a supervisor at Everserved. She is a graduate of Lagos State University (LASU), She hails from Owerri in Imo State..
Egbujor Christopher is
Lorem ipsum dolor, sit amet consectetur adipisicing elit. Quidem architecto consequuntur ratione, obcaecati corrupti deserunt.
Lorem ipsum dolor, sit amet consectetur adipisicing elit. Quidem architecto consequuntur ratione, obcaecati corrupti deserunt.
Lorem ipsum dolor, sit amet consectetur adipisicing elit. Quidem architecto consequuntur ratione, obcaecati corrupti deserunt.
Lorem ipsum dolor, sit amet consectetur adipisicing elit. Quidem architecto consequuntur ratione, obcaecati corrupti deserunt.


Current Round
Last Round
Bid by: {{d.sender}}
Amount: {{d.amount}} {{d.currency}}
Author: {{d.author}}
{{d.url}}Weightage: {{d.weight/100}}%
Bid by: {{d.sender}}
Amount: {{d.amount}} {{d.currency}}
Author: {{d.author}}
{{d.url}}Weightage: {{d.weight/100}}%


Check out Pikarange for a single range picker. This one is for trickier range picking, like when only a handful of dates are available to pick from.
Since version 1.0 Pikaday is a stable and battle tested date-picker. Feel free to use it however you like but please report any bugs or feature requests to the GitHub issue tracker, thanks!
Hinderling Volkart AG | BSD & MIT license | Copyright © 2014 David Bushell | BSD & MIT license | Example by Ramiro Rikkert


Data Tracking
Sometimes Google Analytics page views just don't cut it. You need funnels, dashboards & cohort analysis to reach timely actionable conclusions.
Sometimes Google Analytics page views just don't cut it. You need funnels, dashboards & cohort analysis to reach timely actionable conclusions.
Autoresponders? Exit intent popups? There are tons of tools out there claiming to improve conversion rates. You need an expert to tell you what would actually work in your business.
Running a split test is easy but data can make you do the wrong thing. I plan and operate optimization plans based on knowledge of statistics which no A/B testing tool can automate.
You probably don't have any shortage of data. What you could use more of is practical, relevant, actionable, data-driven recommendations tailored for your business and resources.
Yuval Qen
Conversion Optimization Expert


Web Admin
Users
Logout
Cesar Espinosa's
House
Select a user
+ ZONE
Zones
Living Room
Kitchen
Bathroom
Main Room
Kids Room
Studio/Office


|
ClusterDuck Protocol
|
There are two fundamental components of the pull request process: one concrete and technical, and one more process oriented. The concrete and technical component involves the specific details of setting up your local environment so that you can make the actual changes. This is where we will start.
More details to come on ClusterDuck-Protocol dependencies. In case of doubt, open an issue in the issue tracker or engage on the ClusterDuck-Protocol Slack workspace.
To get started, you will need to have git
installed locally. Depending on your operating system, there are also a number of other dependencies required.
Once you have git
and are sure you have all of the necessary dependencies, it's time to create a fork.
Fork the project on GitHub and clone your fork locally.
You will need to have Git Large File Storage installed locally.
It is recommended to configure git
so that it knows who you are:
You can use any name/email address you prefer here. We only use the metadata generated by git
using this configuration for properly attributing your changes to you in the AUTHORS
file and the changelog.
As a best practice to keep your development environment as organized as possible, create local branches to work within. These should also be created directly off of the master
branch.
ClusterDuck-Protocol does not yet have a style guide. If you're interested in creating one, you're on the right page 😃
It is a recommended best practice to keep your changes as logically grouped as possible within individual commits. There is no limit to the number of commits any single pull request may have, and many contributors find it easier to review changes that are split across multiple commits.
Note that multiple commits often get squashed when they are landed (see the notes about commit squashing).
A good commit message should describe what changed and why. One line commits are good, but if you want to go into more detail:
The first line should:
git log --oneline files/you/changed
to find out what subsystems your changes touch.Examples:
net: add localAddress and localPort to Socket
src: fix typos in async_wrap.h
Fixes:
prefix and the full issue URL. For other references use Refs:
.Sample complete commit message:
If you are new to contributing to ClusterDuck-Protocol, please try to do your best at conforming to these guidelines, but do not worry if you get something wrong. One of the existing contributors will help get things situated and the contributor landing the pull request will ensure that everything follows the project guidelines.
As a best practice, once you have committed your changes, it is a good idea to use git rebase
(not git merge
) to synchronize your work with the main repository.
This ensures that your working branch has the latest changes from master.
Instructions should also be provided so that the core team can validate the change.
Once you are sure your commits are ready to go, with passing tests and linting, begin the process of opening a pull request by pushing your working branch to your fork on GitHub.
From within GitHub, opening a new pull request will present you with a few form fields.
Please try to do your best at filling out the details, but feel free to skip parts if you're not sure what to put.
Once opened, pull requests are usually reviewed within a few days.
You will probably get feedback or requests for changes to your pull request. This is a big part of the submission process so don't be discouraged! Some contributors may sign off on the pull request right away, others may have more detailed comments or feedback. This is a necessary part of the process in order to evaluate whether the changes are correct and necessary.
To make changes to an existing pull request, make the changes to your local branch, add a new commit with those changes, and push those to your fork. GitHub will automatically update the pull request.
It is also frequently necessary to synchronize your pull request with other changes that have landed in master
by using git rebase
:
Important: The git push --force-with-lease
command is one of the few ways to delete history in git
. Before you use it, make sure you understand the risks. If in doubt, you can always ask for guidance in the pull request or on the ClusterDuck-Protocol Slack workspace.
If you happen to make a mistake in any of your commits, do not worry. You can amend the last commit (for example if you want to change the commit log).
There are a number of more advanced mechanisms for managing commits using git rebase
that can be used, but are beyond the scope of this guide.
Feel free to post a comment in the pull request to ping reviewers if you are awaiting an answer on something. If you encounter words or acronyms that seem unfamiliar, refer to this glossary.
All pull requests require "sign off" in order to land. Whenever a contributor reviews a pull request they may find specific details that they would like to see changed or fixed. These may be as simple as fixing a typo, or may involve substantive changes to the code you have written. While such requests are intended to be helpful, they may come across as abrupt or unhelpful, especially requests to change things that do not include concrete suggestions on how to change them.
Try not to be discouraged. If you feel that a particular review is unfair, say so, or contact one of the other contributors in the project and seek their input. Often such comments are the result of the reviewer having only taken a short amount of time to review and are not ill-intended. Such issues can often be resolved with a bit of patience. That said, reviewers should be expected to be helpful in their feedback, and feedback that is simply vague, dismissive and unhelpful is likely safe to ignore.
In order to land, a pull request needs to be reviewed and [approved][] by at least one ClusterDuck-Protocol Collaborators. After that, as long as there are no objections from other contributors, the pull request can be merged. If you find your pull request waiting longer than you expect, see the notes about the waiting time.
When a collaborator lands your pull request, they will post a comment to the pull request page mentioning the commit(s) it landed as. GitHub often shows the pull request as Closed
at this point, but don't worry. If you look at the branch you raised your pull request against (probably master
), you should see a commit with your name on it. Congratulations and thanks for your contribution!
All ClusterDuck-Protocol contributors who choose to review and provide feedback on pull requests have a responsibility to both the project and the individual making the contribution. Reviews and feedback must be helpful, insightful, and geared towards improving the contribution as opposed to simply blocking it. If there are reasons why you feel the PR should not land, explain what those are. Do not expect to be able to block a pull request from advancing simply because you say "No" without giving an explanation. Be open to having your mind changed. Be open to working with the contributor to make the pull request better.
Reviews that are dismissive or disrespectful of the contributor or any other reviewers are strictly counter to the Code of Conduct.
When reviewing a pull request, the primary goals are for the codebase to improve and for the person submitting the request to succeed. Even if a pull request does not land, the submitters should come away from the experience feeling like their effort was not wasted or unappreciated. Every pull request from a new contributor is an opportunity to grow the community.
Do not overwhelm new contributors.
It is tempting to micro-optimize and make everything about relative performance, perfect grammar, or exact style matches. Do not succumb to that temptation.
Focus first on the most significant aspects of the change:
When changes are necessary, request them, do not demand them, and do not assume that the submitter already knows how to add a test or run a benchmark.
Specific performance optimization techniques, coding styles and conventions change over time. The first impression you give to a new contributor never does.
Nits (requests for small changes that are not essential) are fine, but try to avoid stalling the pull request. Most nits can typically be fixed by the ClusterDuck-Protocol Collaborator landing the pull request but they can also be an opportunity for the contributor to learn a bit more about the project.
It is always good to clearly indicate nits when you comment: e.g. Nit: change foo() to bar(). But this is not blocking.
If your comments were addressed but were not folded automatically after new commits or if they proved to be mistaken, please, [hide them][hiding-a-comment] with the appropriate reason to keep the conversation flow concise and relevant.
Be aware that how you communicate requests and reviews in your feedback can have a significant impact on the success of the pull request. Yes, we may land a particular change that makes ClusterDuck-Protocol better, but the individual might just not want to have anything to do with ClusterDuck-Protocol ever again. The goal is not just having good code.
There is a minimum waiting time which we try to respect for non-trivial changes, so that people who may have important input in such a distributed project are able to respond.
For non-trivial changes, pull requests must be left open for at least 48 hours. In most cases, when the PR is relatively small and focused on a narrow set of changes, that will provide more than enough time to adequately review. Sometimes changes take far longer to review, or need more specialized review from subject matter experts. When in doubt, do not rush.
Trivial changes, typically limited to small formatting changes or fixes to documentation, may be landed within the minimum 48 hour window.
If a pull request appears to be abandoned or stalled, it is polite to first check with the contributor to see if they intend to continue the work before checking if they would mind if you took it over (especially if it just has nits left). When doing so, it is courteous to give the original contributor credit for the work they started (either by preserving their name and email address in the commit log, or by using an Author:
meta-data tag in the commit.
Any ClusterDuck-Protocol core Collaborator (any GitHub user with commit rights in the Call-for-Code/ClusterDuck-Protocol
repository) is authorized to approve any other contributor's work. Collaborators are not permitted to approve their own pull requests.
Collaborators indicate that they have reviewed and approve of the changes in a pull request either by using GitHub's Approval Workflow, which is preferred, or by leaving an LGTM
("Looks Good To Me") comment.
When explicitly using the "Changes requested" component of the GitHub Approval Workflow, show empathy. That is, do not be rude or abrupt with your feedback and offer concrete suggestions for improvement, if possible. If you're not sure how a particular change can be improved, say so.
Most importantly, after leaving such requests, it is courteous to make yourself available later to check whether your comments have been addressed.
If you see that requested changes have been made, you can clear another collaborator's Changes requested
review.
Change requests that are vague, dismissive, or unconstructive may also be dismissed if requests for greater clarification go unanswered within a reasonable period of time.
If you do not believe that the pull request should land at all, use Changes requested
to indicate that you are considering some of your comments to block the PR from landing. When doing so, explain why you believe the pull request should not land along with an explanation of what may be an acceptable alternative course, if any.
Opinions on this vary, even among the members of the Technical Steering Committee.
One general rule of thumb is that if ClusterDuck-Protocol itself needs it (due to historic or functional reasons), then it belongs in ClusterDuck-Protocol.
Also, functionality that either cannot be implemented outside of core in any reasonable way, or only with significant pain.
It is not uncommon for contributors to suggest new features they feel would make ClusterDuck-Protocol better. These may or may not make sense to add, but as with all changes, be courteous in how you communicate your stance on these. Comments that make the contributor feel like they should have "known better" or ridiculed for even trying run counter to the Code of Conduct.
ClusterDuck-Protocol has always optimized for speed of execution. If a particular change can be shown to make some part of ClusterDuck-Protocol faster, it's quite likely to be accepted. Claims that a particular pull request will make things faster will almost always be met by requests for performance [benchmark results][] that demonstrate the improvement.
That said, performance is not the only factor to consider. ClusterDuck-Protocol also optimizes in favor of not breaking existing code in the ecosystem, and not changing working functional code just for the sake of changing.
If a particular pull request introduces a performance or functional regression, rather than simply rejecting the pull request, take the time to work with the contributor on improving the change. Offer feedback and advice on what would make the pull request acceptable, and do not assume that the contributor should already know how to do that. Be explicit in your feedback.
Every pull request needs to be tested to make sure that it works on the platforms that ClusterDuck-Protocol supports. This is currently done manually, but automated testing may come soon.
In most cases, do not squash commits that you add to your pull request during the review process. When the commits in your pull request land, they may be squashed into one commit per logical change. Metadata will be added to the commit message (including links to the pull request, links to relevant issues, and the names of the reviewers). The commit history of your pull request, however, will stay intact on the pull request page.
For the size of "one logical change", 0b5191f can be a good example. It touches the implementation, the documentation, and the tests, but is still one logical change. All tests should always pass when each individual commit lands on the master branch.
A pull request is approved either by saying LGTM, which stands for "Looks Good To Me", or by using GitHub's Approve button. GitHub's pull request review feature can be used during the process. For more information, check out the video tutorial or the official documentation.
After you push new changes to your branch, you need to get approval for these new changes again, even if GitHub shows "Approved" because the reviewers have hit the buttons before.
Every pull request needs to be tested to make sure that it works on the platforms that ClusterDuck-Protocol supports. This is currently done manually, but automated testing may come soon.
A pull request needs to stay open for at least 48 hours from when it is submitted, even after it gets approved and passes the CI. This is to make sure that everyone has a chance to weigh in. If the changes are trivial, collaborators may decide it doesn't need to wait. A pull request may well take longer to be merged in.


This is a work in progress project that allows you to float a note taking window over a website. This utility does not support websites that do not allow their content to be shown in an iFrame.
Known S\sites that do not allow embeding in an iFrame:
Some known workarounds to this problem include:
http://youtube.com/embed/{{videoid}}


Having a document read to you
You can have CocoaPad read your text to you. No, you can't speak the text and have it appear in your document. You'll need some $400 program (like Dragon NaturallySpeaking, which ain't for Macs, by the way) that do this.
To have CocoaPad read your document:
- Choose Start Speaking from the Edit > Speech menu.
If you select some text, CocoaPad will only read the selected text. You can also have CocoaPad start over in the middle of reading by selecting Start Speaking again. |


Cupcake Ipsum.
Muffin sweet tart tootsie roll toffee muffin dragée muffin. Gingerbread ice cream biscuit cupcake. Candy chocolate bar caramels icing liquorice pie halvah. Jujubes jelly-o jujubes. Lollipop halvah sugar plum biscuit lollipop icing biscuit sugar plum candy canes. Gingerbread tiramisu sugar plum. Danish cake marzipan gummi bears danish halvah pie dessert. Chocolate cake danish brownie bear claw fruitcake soufflé carrot cake. Jelly beans danish cake cupcake sesame snaps chupa chups. Halvah sweet tiramisu pie candy danish cheesecake pastry icing. Brownie marshmallow chocolate bar cake toffee apple pie sugar plum oat cake. Oat cake tootsie roll dessert cheesecake chupa chups cookie.


JABAWS MANUAL
JABAWS Usage Statistics
- Summary of Usage
- Authentication
- Detailed Usage Statistic
- Job List
- Single Job Directory Content
- Configuring a privileged access for Tomcat web application server
- Configuring JABAWS execution statistics
Summary of Usage
JABAWS comes with a web application for visualizing usage statistics. The screenshot below shows the main page of this application. Each month is a link to the detailed usage statistics for this month described later. Please note however, that the links to the detailed monthly statistics are only available for authenticated users in the role admin. There is a link at the bottom of the page that would let you login, if you have not done so.
If you are using JABAWS VA (Virtual Appliance) then the username is jabaws and password is not defined, e.g. empty.
If you have deployed a JABAWS WAR file, then please see the configuring privileged access for Tomcat web application server section for further details.
The table contains the number of jobs processed by JABAWS per month, for the whole period when the statistics was collected
For each month the table contains the following information.
- Month - the period of time for which statistics is displayed. For example Jan 2011 means period of time from the first of January to the first of February.
- Total - the total number of jobs accepted by JABAWS
- Incomplete - the number of jobs for which the result file was not found or was empty excluding cancelled
- Cancelled - the number of jobs cancelled by the user
- Abandoned - the number of jobs which result(s) were not collected
The summary for each column is displayed in the last row of the table.
Authentication
Authentication lets you see the detailed usage statistics. If you are using JABAWS VA (Virtual Appliance) then the username is jabaws and password is not defined, e.g. empty. In other cases you need to ask your system administrator for it.
Detailed Usage Statistic
Detailed execution statistics for each month is available for authenticated users only.
Each table contains the number of jobs processed by JABAWS during the period of time specified in the title.
- The "All Jobs" table contains the summary of all jobs.
- "Local Jobs" table - contains the summary of the jobs calculated by the local engine.
- "Cluster Jobs" table - contains the summary of the jobs calculated by the cluster.
- Total - the total number of jobs accepted by a particular JABA service
- Incomplete - the number of jobs for which the result file was not found or was empty excluding cancelled
- Cancelled - the number of jobs cancelled by the user
- Abandoned - the number of jobs which result(s) were not collected
Job List
Please note that if you deployed JABAWS WAR, in order to be able to navigate to the job directory from this view the application server may need to be configured. Please see Configuring JABAWS execution statistics section for further details.
Columns
- JobID - the JABAWS job id, unique for every job
- Cluster JobID - cluster job id
- InputSize - input size in bytes
- ResultSize - result size in bytes
- Runtime (s) - job's runtime in seconds
- Start time (s)- job's start time and date
- Finish time (s)- job's finish time and date
- isCancelled - whether the job was cancelled
- isCollected - whether the job was collected. False for the jobs that has been initiated but which results has never been retrieved
- isFinished - whether the job has finished. This does not necessarily mean that the job has produced the result. The job can sometime finish in failure.
JABAWS Job Directory Content
STARTED and FINISHED files contain Unix timestamp - when the job was started and completed respectively. STARTED is replaced by SUBMITTED if the job has been submitted to the cluster, as opposed to executed locally, on the server.
COLLECTED file is empty and indicates that the job results were collected by the user. Due to asynchronous nature of the job it is possible that the job was started and finished, but the results has never been requested.
RunnerConfig.xml file contains a complete description of the job and JABAWS can restart the job based on this description.
procError.txt and procOutput.txt files contains the content of the standard out and standard error streams of the process.
result.txt file contains the results.
input.txt file contains input into the process.
There are maybe other files depending on the nature of the job, but the one described above will present in most cases. In this example, stat.log file stories the execution statistics generated by the process (clustal executable in this example).
If you have deployed JABAWS WAR file or made changes to JABAWS configuration you may need to make a few changes to the Tomcat configuration to be able to see the content of the job directory. Please see Configuring JABAWS execution statistics section for further details.
Configuring JABAWS execution statistics
JABAWS execution statistics is a multi-component system. First is a crawler which job is to collect and preprocess the statistics from the job temporary directories and record the collected statistics into the database. The second part of the system is a web application which job is to visualise the statistics from the database.
It is possible to enable/disable the statistics collector by changing the following properties in the conf/Cluster.engine.properties and conf/Local.engine.properties files.
# Enable/disable cluster statistics collector true = enable, false = disable
cluster.stat.collector.enable=false
# Maximum amount of time the job is considered be running in hours. Optional defaults to 7 days (168h)
cluster.stat.maxruntime=24
# Enable/disable cluster statistics collector true = enable, false = disable
local.stat.collector.enable=true
# Maximum amount of time the job is considered to be running in hours. Optional defaults to 24 hours
local.stat.maxruntime=6
If the statistics collector is enabled then the crawler starts automatically soon after (10 minutes for local engine, and 60 minutes for cluster engine) the JABAWS web application and will be collecting the execution statistics every 24 hours after the start.
The details of the job are only available if the job temporary directory is located within a JABAWS web application. If not, the system administrator can create a symbolic link pointing to the temporary job directories outside of a web application and configure the application server to allow navigation to the links. For the Tomcat application server the context configuration file should be created and copied to the <TOMCAT_ROOT>/conf/Catalina/localhost directory. The name of the file should be the same as the web application context name, for example "jabaws.xml" for jabaws. Where the TOMCAT_ROOT is the location of the Tomcat web application server. Here is an example of such a file:
<?xml version="1.0" encoding="UTF-8"?>
<Context antiResourceLocking="false" privileged="true" allowLinking="true"/>
The key option here is this: allowLinking="true". Please also make sure that you have defined the user in role "admin" as described below.
Configuring a privileged access for Tomcat web application server
Access to configuration files, detailed job execution statistics and job directories are allowed only for authenticated users in role "admin".
If you use Tomcat, then the simplest way to set up privileged access is to use a plain text configuration file conf/tomcat-user.xml. Here is an example of such configuration file defining user "peter" in role "admin". <tomcat-users>
<role rolename="admin"/>
<user username="peter" password="your password here " roles="admin"/>
</tomcat-users>
For more information on users and roles please consult Apache-Tomcat help pages.


App
work
supervisor_account
recent_actors
Luiz
perm_identity
account_circle
About
settings
Settings
settings_power
Name
email
Foo
<EMAIL_ADDRESS>edit
delete
New
add
New
account_circle
Name
email
Email


Hello! This exporter downloads an xlsx file that contains the current professor's publications and checks its policies.


--- layout: post title: Keeping me in a flow state this week... date: 2009-02-18 00:00:00 categories: amusing digital-media interfaces-&-interaction mobile social software-development ---


Man climbed onto parapet to film woman showering in flat
by Lydia LamSINGAPORE: A man climbed onto a parapet to watch a woman showering and later used his phone to film the victim for "a better view".
For insulting the modesty of this 23-year-old woman, along with two others, 27-year-old Mohamed Noor Hakim Mohamed Jamal was sentenced to nine weeks' jail on Monday (Nov 11).
The court heard that Hakim was a despatch rider at the time of the offences.
He had targeted three victims, aged 23, 22 and 18, once every year since 2017.
The first incident occurred on the night of Aug 29, 2017, when Hakim was playing with his nieces at a playground in a housing estate.
All locations were redacted from court documents to protect the victims' identities.
He noticed that the lights were switched on in a toilet at a flat and had an urge to peep inside, said Deputy Public Prosecutor Benedict Chan.
He climbed onto the ledge of the parapet located outside of the toilet and peeped in, but could see only the head and shoulders of a woman inside.
Court documents did not state which floor this occurred at.
In order to get a better view of the victim, Hakim took a video recording of the woman with his phone, before returning to his nieces at the playground.
After watching it, he deleted the video as he feared being caught with it.
However, a neighbour saw Hakim walking up and down the corridor and taking a picture of video of the toilet, and reported the incident to the police.
Hakim went on to offend a second time more than a year later on Nov 6, 2018.
TARGETS SECOND VICTIM A YEAR LATER
He stood along the corridor outside a flat and watched a 22-year-old woman taking off her clothes.
The woman told her brother-in-law what happened, and he tried to catch Hakim but did not manage to, as he had left.
The family aimed their closed-circuit television camera towards the location where Hakim and been, and successfully caught him trying to peek into the unit again four days later.
He was arrested and admitted to peeping into the victim's ninth-floor unit several times.
The third incident occurred on Aug 7 this year, while Hakim was on his way to visit his sister.
He cycled past a flat that he was familiar with, as he had seen a girl inside when he broke into the house in 2017.
He parked his bicycle a few blocks away and went to the unit, carefully avoiding police cameras along the way, said the prosecutor.

He extended his phone through the ajar toilet window to record the 18-year-old girl showering.
The girl saw his hand and the phone and screamed, prompting Hakim to flee.
He admitted to committing the offences to "satisfy his sexual urges".
The prosecution asked for 11 weeks' jail, saying that Hakim's multiple offences over three years "demonstrated his persistent voyeuristic ways".
"The accused has no psychiatric illness or disorder, and his urges were not uncontrollable," he said.
Hakim had tried to destroy evidence by deleting video footage of two victims, and had intentionally avoided police cameras to evade detection.
For each count of intruding on the privacy of a woman to insult her modesty, Hakim could have been jailed for up to a year, fined, or both.