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.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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |