Hi CMCN1982,
You can use SQL server or Oracle to hold the metadata of jasper soft, in-case you use SQL 2008R2. you have to upgrade to Microsoft SQL Server 2012 as Jasper soft supported with only that. You have to create a database for jasper soft and grant few privileges to that schema.
SQL Server
Follow these steps:
1. Create a database user. For example, PPM_JASPERSOFT.
2. Alter database ppm_jaspersoft set arithabort On.
3. Alter database ppm_jaspersoftsoft set ansi_nulls On.
4. Alter database ppm_jaspersoft set quoted_identifier On.
IF (SELECT (CAST(LEFT(CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR(20)), CHARINDEX('.', CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR(20)), 1) - 1) AS INTEGER))) = 10
BEGIN
exec sp_dbcmptlevel 'PPM_JASPERSOFT', @new_cmptlevel=100
END
IF (SELECT (CAST(LEFT(CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR(20)), CHARINDEX('.', CAST(SERVERPROPERTY('ProductVersion') AS VARCHAR(20)), 1) - 1) AS INTEGER))) = 11
BEGIN
exec sp_dbcmptlevel 'PPM_JASPERSOFT', @new_cmptlevel=110
END
IF NOT EXISTS (SELECT 'yes' FROM syslogins WHERE LOWER(name) = LOWER('PPM_JASPERSOFT') )
BEGIN
exec sp_addlogin 'PPM_JASPERSOFT','password1234','PPM_JASPERSOFT','us_english'
END
Set the isolation level to read committed snapshot for SQL Server 2005.
Note: Make sure that the user can access the system views. For example, syslockinfo, sysindexes.
begin
exec ('alter database PPM_JASPERSOFT set read_committed_snapshot on')
exec ('grant VIEW SERVER STATE to PPM_JASPERSOFT')
exec ('ALTER LOGIN PPM_JASPERSOFT WITH CHECK_POLICY=OFF')
end
USE PPM_JASPERSOFT.
The schema owner is referenced when executing functions in SQL Server and is hard-coded to PPM_JASPERSOFT. However, the login name can differ.
exec sp_grantdbaccess 'PPM_JASPERSOFT','PPM_JASPERSOFT'
Installation Guide
exec sp_defaultdb 'PPM_JASPERSOFT', 'PPM_JASPERSOFT'
exec sp_addrolemember 'db_owner', 'PPM_JASPERSOFT'
And you are all good to go ahead.
Regards
Suman Pramanik