Liberum and sql 2008

[markcuk]

How do you initialize the HelpDesk database with the 'helpdesk.sql' using sql 2008?

 

not used this for a few years and I used access database last time but ii7 does not support it unless i use it in 32bit mode

 

cheers

 

mark

[qcomer]

How do you initialize the HelpDesk database with the 'helpdesk.sql' using sql 2008?

 

not used this for a few years and I used access database last time but ii7 does not support it unless i use it in 32bit mode

 

cheers

 

mark

 

Using Liberum Help Desk with SQL Server Management Studio Express - Liberum Help Desk This should be able to help you. Looks like there should be a .sql file with the query to create the DB. The instructions mention sql express but you can open it the same way in Management Studio for any other 2005/2008 version. Express just has less features.

[qcomer]

This might help also: http://liberum.robatkinson.net/liberum/LinkClick.aspx?fileticket=1p2Lhh5UVrE%3D Not sure what you need help with.

[markcuk]

When i run the sql file in Management Studio I just get errors like

 

Msg 1801, Level 16, State 3, Line 2

Database 'HelpDesk' already exists.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 33003, Level 16, State 1, Line 2

DDL statement is not allowed.

Msg 4902, Level 16, State 1, Line 2

Cannot find the object "dbo.categories" because it does not exist or you do not have permissions.

Msg 4902, Level 16, State 1, Line 2

Cannot find the object "dbo.departments" because it does not exist or you do not have permissions.

Msg 4902, Level 16, State 1, Line 2

Cannot find the object "dbo.priority" because it does not exist or you do not have permissions.

Msg 4902, Level 16, State 1, Line 2

Cannot find the object "dbo.problems" because it does not exist or you do not have permissions.

Msg 4902, Level 16, State 1, Line 2

Cannot find the object "dbo.status" because it does not exist or you do not have permissions.

Msg 4902, Level 16, State 1, Line 2

Cannot find the object "dbo.tblConfig_Auth" because it does not exist or you do not have permissions.

Msg 4902, Level 16, State 1, Line 2

Cannot find the object "dbo.tblConfig_Email" because it does not exist or you do not have permissions.

Msg 4902, Level 16, State 1, Line 2

Cannot find the object "dbo.tblEmailMsg" because it does not exist or you do not have permissions.

Msg 4902, Level 16, State 1, Line 2

Cannot find the object "dbo.tblUsers" because it does not exist or you do not have permissions.

Msg 4902, Level 16, State 1, Line 2

Cannot find the object "dbo.tblUsers" because it does not exist or you do not have permissions.

Msg 208, Level 16, State 1, Line 2

Invalid object name 'tblconfig'.

Msg 208, Level 16, State 1, Line 2

Invalid object name 'tblConfig_Auth'.

Msg 208, Level 16, State 1, Line 2

Invalid object name 'tblConfig_Email'.

Msg 208, Level 16, State 1, Line 2

Invalid object name 'tblEmailMsg'.

Msg 208, Level 16, State 1, Line 2

Invalid object name 'tblUsers'.

Msg 208, Level 16, State 1, Line 2

Invalid object name 'db_keys'.

Msg 208, Level 16, State 1, Line 2

Invalid object name 'status'.

Msg 208, Level 16, State 1, Line 2

Invalid object name 'priority'.

Msg 208, Level 16, State 1, Line 2

Invalid object name 'departments'.

Msg 208, Level 16, State 1, Line 2

Invalid object name 'tblLanguage'.

 

help?

[markcuk]

okay i can now access the update database part but it fails with error Invalid object name 'tblConfig'.

 

I still need to do something with helpdesk.sql file but cannot get it to run the script without errors

[qcomer]

okay i can now access the update database part but it fails with error Invalid object name 'tblConfig'.

 

I still need to do something with helpdesk.sql file but cannot get it to run the script without errors

 

It looks like you already have a DB with that name. You can open the .sql file in Notepad (I recommend notepad ++ ) or straight into management studio and edit it there. I recommend reading their installation instructions that Liberum has available.

[theriver]

When i run the sql file in Management Studio I just get errors like

 

Msg 1801, Level 16, State 3, Line 2

Database 'HelpDesk' already exists.

 

So, as qcomer says, this means that the database already exists. Often you will find that running a script twice will break something (e.g. insert duplicate system data or lookup data into some table), so in general if the script doesn't work first time out, instead of re-running it's safer to roll back to your previous state. In this case it looks like you can delete the 'helpdesk' database you've just created and try again.

 

The 'invalid object name' and 'DDL' stuff makes me wonder if you're inadvertantly running the script this subsequent time against the wrong database - have a look at the dropdown that's underneath 'New Query' and to the left of "!Execute" - that's the database your current query window is going to run stuff in.

 

In any case, I'd say: drop the database and try running the script again, once only. If it fails, post the errors up here.