Hi David,
Can you give me the mssql scripts for 2.1.1.
Regards
Nishant 

-----Original Message-----
From: David Sean Taylor (JIRA) [mailto:[email protected]] 
Sent: Wednesday, September 30, 2009 12:29 AM
To: Malviya, Nishant (STSD)
Subject: [jira] Updated: (JS2-1067) Jetspeed 2.1.1 with MSSQL Server


     [ 
https://issues.apache.org/jira/browse/JS2-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

David Sean Taylor updated JS2-1067:
-----------------------------------

    Attachment: schema.zip

> Jetspeed 2.1.1 with MSSQL Server
> --------------------------------
>
>                 Key: JS2-1067
>                 URL: https://issues.apache.org/jira/browse/JS2-1067
>             Project: Jetspeed 2
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: 2.1.1-RC
>         Environment: Windows 2003 Server
>            Reporter: Nishant Malviya
>            Assignee: David Sean Taylor
>            Priority: Critical
>             Fix For: 2.1.1-RC
>
>         Attachments: schema.zip
>
>
> I am unable to configure jetspeed 2.1.1 with MS-SQL server 2000-3a database 
> server.
> I did the following steps to configure jetspeed: 
> Step 1: I have created the database using the scripts given in the product.
>  the script had to be modified little to remove ON DELETE CASCADE to ON 
> DELETE NO ACTION in some the of the tables. after making that change the 
> database got created. but don't know if this will impact jetspeed.
> Step 2: I tried to modify the database.properties with MSSQl driver and 
> database information but still its taking derby as database.
> Can you tell me the steps needed to configure jetspeed with this database. I 
> cannot modify maven file and generate jetspeed as this jetspeed is deployed 
> on customer site.

--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to