If the TIBCO Scribe® Insight ScribeInternal database has grown beyond 500 MB then you should start investigating why the growth is occurring.
The problem could be related to data in various tables or the growth of the SQL Transaction Log file.
This information can be obtained from SQL Server Management Studio.
However the attached scripts make it easier to see the information in a single view.

Data - Typically data growth is caused by the following:

• Large number of entries in the logging tables (ExecutionLog, TransactionErrors, AlertLog)
• Rejected Row tables (they could be named anything)

      See Scribemaintenance.sql in the TIBCO Scribe® Insight Help for managing the logging tables. The Rejected Row tables must be manually maintained.
       

ScribeInternal Database Transaction Log File

   This is the log file created by SQL server for the database
   If the Full recovery model is utilized this file can continue to grow until a Transaction Log file backup is taken in SQL Server

The List SQL Server DB File Info.sql script lists all databases and their corresponding file sizes
The List SQL DB Table Info.sql script lists the number of rows and the size of each table (must select the appropriate database in SSMS)