You need to do this for each range of tickets that you want to remove. You will be deleting tickets 1647 to 1650 inclusive, correct?ĭelete only (c)losed or (a)ll tickets in range? (closed keeps any open or waiting tickets in the range)ĭeleting closed tickets from 1647 to 1650 inclusive This is the output I got from running it for tickets between 16.
![install spiceworks sql server install spiceworks sql server](https://i0.wp.com/techdirectarchive.com/wp-content/uploads/2018/07/picture111.png)
Following that is a confirmation prompt (do check that carefully!) and finally, whether you should only remove closed tickets. The next prompt is which ticket number to start at, then which ticket number to end with. Here, type in 2 (since we are going to be removing a range of tickets).
![install spiceworks sql server install spiceworks sql server](https://content.spiceworksstatic.com/service.community/p/cms_microsite_attachments/0000002699/5d6640d1/attached_file/Generate_SecretKey.png)
After some possible errors (see below in the Gotchas), you should view something like this: Spiceworks Ticket Loop Tool Notice that there are no command line options (which is a shame) so you will now be using this tool interactively. You might have seen that in the main folder there is a file named ticket_delete.exe that’s the command which is going to do all the work for us so let’s move onto that. Take a copy of that and store it somewhere safe - it contains the SQLite database file, backups and other files which you may need if things turn sour. Let’s now go to the directory Spiceworks is installed in, and there, you should see a folder named db. OK, the server has been removed from the running processes. By the way, there are methods you can use which use the GUI, but ultimately, the command line is best in my opinion because you are closer to the core commands that are often really run, anyway, and don’t have to contend with any HTTP timeouts etc. This should fairly quickly stop the server. Start this and then type the following command: > net stop spiceworks We’re going to shut down Spiceworks next and to do that you will need an administrator shell on the server that your installation resides. You should now either have a start an end number for the tickets, or a whole set of of them, if there were any gaps in the sequences. I’m sure there are many other ways, but hopefully one of these will suffice. Lastly, you could see which was the latest ticket ID (that would be your max) and then use the range: 1 to that max number.Go directly to the database backend (see DB Browser below).Then, take the smallest and greatest for your range. Create/use a report in the GUI to show a list of closed tickets, ordered by ID.
![install spiceworks sql server install spiceworks sql server](https://i0.wp.com/www.technig.com/wp-content/uploads/2016/10/SolarWinds-SQL-Server-Monitoring-Technig.png)
You’ve got many options here but you could either: To start, let’s find out what range(s) of ticket numbers you have. Getting Candidate Tickets to Deleteįirstly, let’s remove the unwanted (old, closed) tickets from the database (if you want to keep them, you can use the backup database in a second instance). Spiceworks has an SQLite database to store all the information about tickets, but use it for a while, and soon you will end up with a huge file which causes Spiceworks to slow down or even crash.