How to make massive changes to electronic election results

If there's no database transaction log, there won't be any record of those changes either.

Databases are an area of my professional expertise. I first saw database software back in the 1980s but didn’t do much with it. I first started working with databases on the job almost 30 years ago. That was with a proprietary database that also had custom commands to change the data in the data tables. A couple years later I wrote my first code to transfer data into a database. About a year after that I was creating an Access database to hold test data, and then developed an interface to pull out that data and automatically generate reports in Excel.

A couple more years down the road and I’m developing a Microsoft SQL Server database to hold semiconductor test data, and at the same time coding a program to extract that data in various ways, again including automated reports in Excel and this time PowerPoint as well. Later I added automation for something called JMP, which is a much more advanced program than Excel. My development of the database and the data viewing program, and issues with data that got loaded into the database, required occasional changes to the data in the various tables in the database.

Early on to make any changes to data I just used a Microsoft program called ‘SQL Server Management Studio’. This is the same program I used to create the database and the data tables in the first place, and of course for any changes to the table structures down the line. While the Management Studio program has “GUI” style tools for some tasks, it also allows you to use a database language called ‘Structured Query Language’ that can be used to create and change objects and data in databases, and that’s where the “SQL” acronym comes from.

SQL is a fairly simple language to learn for basic tasks like selecting specific data and changing data in tables. If there was a table for all voters, you could select all voters and order them alphabetically with this very simple query:

SELECT DISTINCT LastName, FirstName

FROM Voters

ORDER BY LastName, FirstName

In that case the name of the table is “Voters”, and “LastName” and “FirstName” are fields in that table. In an actual data table of registered voters of course there would be addresses, birth dates, and a voter ID number of some sort as well, but you get the idea of how simple it is to select data with a query like that. And with SQL you get to select only the fields you are interested with any SELECT query.

What if you want to change data? Well that is very simple as well. If you wanted to change the zip codes for a bunch of voters just prior to when ballots would be mailed out such that they wouldn’t get delivered, you could change every record from one zip code to another:

UPDATE Voters SET ZipCode = '12345'

WHERE ZipCode = ‘67890’

I’m using this example because this exact thing happened and was discovered because there is an organization tracking some voter registration databases on a regular basis, and they caught where 31,000 zip codes were changed just before ballots were mailed out, and then they were changed back so there would be no record of the temporary change unless someone was doing regular downloads of the data. Of course the vast majority of those ballots would not be delivered to the intended recipients, and many would instead be available for collection by ballot mule organizations.

What about changing voting results? Well of course that’s easy too.

UPDATE VoteResults

SET PresidentVote = 'Biden'

WHERE PresidentVote = 'Trump' AND Precinct = ‘17’

Of course I’m making up obvious examples for the table name and the field names, and it does not make any difference whatsoever if those names are different or if the table structure is different. In my example every vote for Trump in precinct 17 would be changed to a Biden vote, and the SQL statement could easily be changed for any different naming method or data storage method. The changes would be trivial.

If you think changing every vote in one precinct would be too obvious, note you can use what is called the modulus operator on the numeric index field that should be there in voting tables, and only change every 20th vote, or every 15 vote, or every however many votes you think you need to change in order to change the outcome of the race(s) you want to change, and when you’re done there will be no record of the changes you made. Numerous other criteria could be used to make vote changes more random as well.

A “risk limiting audit” that confirms that the scanning machines are recording the votes as cast is not going to catch this sort of fraud either, because it happens after the scanning process and after the votes are recorded in the database. It’s not part of the installed machine code either. It’s a manual act that can be done by someone with local access or by remote access. And there will be no record of the changes either, since it has been established that the voting database servers looked at in the past did not have something called a “transaction log” that captured changes to data in the tables.

Even if there were transaction logs kept at any point, if someone with the right privileges has access to the database server locally or remotely, they can overwrite or delete those transaction logs. And queries like this can be pre-written and run in a matter of seconds to a couple of minutes, depending on the number of records to be changed and the server hardware. If the data tables only keep vote totals it’s even faster and easier. The query could be something like:

UPDATE VoteResults

SET TrumpVote = TrumpVote * 0.995

BidenVote = BidenVote * 1.005

In SQL the asterisk is the multiplication symbol, and the example above shows 1/2 of 1% of Trump votes being switched to Biden. This query could be run multiple times as needed (over a few hours so the changes are small) to change the outcome, or a larger percentage change could be used to do it in one shot. Note that it does not matter if any particular database versions needs the initial vote field values to be assigned to a temporary variable first. It is still very trivial to do this and if there is only a summation of all votes per precinct or per county or per whatever, this query takes less than one second to run.

Given what Microsoft SQL Server Management Studio allows you to do so easily in changing the election data, it makes no sense for it to even be installed on election servers. It is not spelled out in the official configuration, and it’s presence indicates an intent to make illegal changes. The database engine to run the database server does NOT require the Management Studio to be installed. It is also true that with remote access to the server, or local access with no observers, you do not need the Management Studio installed on the server to make changes.

When you’re talking about possible electronic changes to vote totals on election servers, Maricopa County Arizona again comes into play, as the entire 2020 election database was deleted from the database server prior even to allowing the sham “audit” the county paid for to proceed. It was right before that pretend audit happened. The “fact checks” on this were so pathetic as to be ridiculous, as those lying left wing “news” sites failed to mention that Ben Cotton was able to recover those files using a program called ‘R-Studio’.

This is also a program I’ve had and used for years, and I used it just recently to recover some files that someone else had accidentally deleted. I’ve used it to recover files many times, and I highly recommend it. It’s not the simplest program to use but there is extensive help available.

The fact that the Maricopa County 2020 database files were easily recovered by an expert using special file recovery software does not change the truth of the deletion, nor does it mitigate the obvious nefarious intent of those involved in deleting the files. Since there was stored video of who was accessing the server, and since Ben Cotton was able to see the deletion date and time, it was also eventually revealed that it was Brian Ramirez who deleted those database files, and he is a database administrator for Maricopa County.

Per the linked Gateway Pundit story, Ramirez himself didn’t have badge access to the election server, and he was never supposed to be in that small room by himself either. But he was given access by others, and he was in there alone, and he did illegally delete those files in defiance of a subpoena from the Arizona Senate. Given all this, why in the hell would anyone in their right mind assume that Ramirez and others did not do more to alter the 2020 election results???

If everything was on the up and up, there was no need to try and stop any audits, and there is certainly no justification at all to illegally delete records that were under subpoena. The only logical conclusion is that Maricopa County personnel participated in the massive democrat fraud in 2020, and of course it was obvious that they had to go even further in 2022.

In the case of the Maricopa County 2020 election database files, I’ve covered this already earlier. The sleazeball RINOs on what I call the Maricopa County Board of Clowns admitted that they deleted the files months later. This admission was captured in this video. It shows two of the sleazeballs admitting to deleting the election database files from the server provided to the audit team under subpoena.

In spite of the admissions in the video from the hearing, you can still find “fact checks” claiming that the 2020 database files were not deleted, and you can still find left wingers repeating those lies. Watch the sleazeballs on the video in the hearing and then compare it to the “fact check” and the lies those sleazeballs told to the “fact checkers” and to the public.

Another fun fact about the Maricopa County election data, per the audit team’s presentation to the AZ senate, there was “Clear Intentional Account Overwriting of the Security Logs by the EMSADMIN Account”:

2/11/21 - 463 entries overwritten.

3/3/21 - 37,686 entries overwritten.

4/12/21 - 330 entries overwritten.

This was done via running a script to overwrite older entries in the log. This is not the same as a database transaction log that I mentioned earlier that would show changes to the election data. It’s far less informative but for whatever reasons Maricopa County personnel needed for those entries to be overwritten to cover up activity on the server. What else would they be covering up but election fraud??

I mentioned Ben Cotton earlier and his company is called CyFIR, and he was charged with the electronic side of the audit of Maricopa County’s 2020 election, and he was far more informative and compelling than the “Cyber Ninjas” on the paper ballot side. His full presentation is at this link, as is considerable additional information refuting the ridiculous claims that the audit “confirmed” Biden “won”. That presentation includes the slides shown below:

Again, why hide all of the above unless the devices and data would show election fraud??

Looking at this slide shows just how easily there could have been hacks, or there could have been tampering after the fact by county personnel or Dominion personnel. After the official Dominion software install, there were a total of 49 executable files (These are usually full programs, even if they require other files to run.) that were created or changed, and over 1400 DLL files (“Dynamic Link Library” These files are very common and contain additional code not found in executable files.) created or changed!!!

Those are MASSIVE changes to the system after the supposedly “certified” software was installed!!! Does that sound like the system is “locked down” or “certified” to you??? At all??? How about no operating system patches? How about outdated virus definitions? How about sharing accounts and passwords such that there is no record of who was actually logged in at any given time?? Does any of the above suggest to you that it is truthful to claim that the 2020 election was “safe and secure”???

The slide above shows you the extent of the deletions from the “C:\” drive just in a one week period in late October and early November of 2020.

Far more files were deleted from this second drive (“D:\”) right before the election until right before the audits.

Data deleted form the ballot scanners.

Far more deletions on scanners 3 and 4, but no deletions on scanner 2. Why??

The log entry overwrites I mentioned earlier, all overwritten by a script looking for blank account passwords, and there were only 16 accounts to check. Running this script over and over was obviously just for the purpose of effectively deleting log entries to cover up evidence of illicit activity. There is no other reason to do something like this.

The sad truth is that in the majority of criminal cases there has to some record of what was deleted or destroyed before it can be used as evidence in court. The Clintons know this very well, which is why they are experts in getting rid of evidence before it can be used against them. Whether it’s a military grade file deletion program that will wipe data away to the point where nothing can retrieve it, or whether it’s a hammer to smash cell phones.

This is a purge of all the election data via the Dominion software. This happened right before the sham “audit” that the County set up. So well before the senate sanctioned audit began. The Clintons would have made sure even this brief log would have disappeared.

There’s much more in Cotton’s presentation if you’ve got the time to check it out. The bottom line is that you should not for one second buy into any claims that the hand ballot count confirmed that the Maricopa County 2020 election was “safe and secure”. Maricopa County went to court and otherwise did everything they could to prevent or at least stall the audit, and that was plenty of time to insert and remove ballots as necessary to get a number close to what the original reported results were.

Keep in mind that there was NO chain of custody for the ballots at all prior to the time they were handed off to the audit team. And don’t forget that Runbeck, the ballot printing company for the county, is only about 15 minutes away from the election center. Runbeck also handles ballots during the election. Unlike computer devices, there is no way to recover evidence of changes to the stored ballots.

Let me know what you think in the comments below.