Editing Installation

Jump to: navigation, search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision Your text
Line 1: Line 1:
 
== Server Requirements ==
 
== Server Requirements ==
  
=== Up to Version 1.02 ===
+
* IIS running on Windows 2000 or higher.
 
+
* ASP.Net 2.0  
* IIS running on Windows 2000 or higher
 
* .Net Framework 2.0  
 
 
* [http://www.codeplex.com/AjaxControlToolkit/Release/ProjectReleases.aspx?ReleaseId=11121 MS Ajax Control Toolkit]
 
* [http://www.codeplex.com/AjaxControlToolkit/Release/ProjectReleases.aspx?ReleaseId=11121 MS Ajax Control Toolkit]
 
* SQL Server 2000 or higher
 
* SQL Server 2000 or higher
* ODP.Net from [http://www.oracle.com/technology/software/tech/windows/odpnet/utilsoft.html Oracle Data Access Components 11g] (optional; required for Oracle connectivity)
 
* Npgsql (optional; required for PostgreSql connectivity)
 
 
=== From Version 1.03 on ===
 
 
* IIS running on Windows XP or higher
 
* .Net 3.5 Service Pack 1
 
* SQL Server 2000 or higher
 
* ODP.Net from [http://www.oracle.com/technology/software/tech/windows/odpnet/utilsoft.html Oracle Data Access Components 11g] (optional; required for Oracle connectivity)
 
* Npgsql (optional; required for PostgreSql connectivity)
 
  
 
== Installation ==
 
== Installation ==
Line 22: Line 10:
 
=== SQL Server ===
 
=== SQL Server ===
  
Open Enterprise Manager (SQL 2000) or SQL Management Studio (SQL 2005+)
+
* Create a database
 
 
* Create a database (select a case-insensitive collation such as Latin1_General_CI_AS)
 
 
* In the database, run the scripts:
 
* In the database, run the scripts:
 
* Create.sql
 
* Create.sql
* Initialize Users.sql
+
* Initialze Users.sql
 
* Value Script.sql
 
* Value Script.sql
 
* Code Snippet.sql
 
* Code Snippet.sql
Line 41: Line 27:
 
* SQL Server authorization
 
* SQL Server authorization
 
* no password policy  
 
* no password policy  
* allow dbo access to the database.
+
* dbo access to the database.
  
 
=== IIS Server ===
 
=== IIS Server ===
  
* Create a directory, virtual directory, and create an application; or create a website in IIS Administrator
+
* Create a directory, virtual directory, or website in IIS Administrator
* Extract web.zip (dbs*webpub.zip) into the directory
+
* Extract web.zip into the directory
* If the zip contains a file called web.publish.config, rename it to web.config
+
* Copy web.config into the directory
* Otherwise, copy web.config into the directory
 
 
* Locate the connection string in web.config and adjust server name, catalog, username, and password.
 
* Locate the connection string in web.config and adjust server name, catalog, username, and password.
 
The web.zip filename is preceded by "dbs" + date + version.
 
 
== Upgrade ==
 
 
=== SQL Server ===
 
 
Open Enterprise Manager (SQL 2000) or SQL Management Studio (SQL 2005+) and locate the existing dbscript database.
 
 
* Open a query window in the database and run the scripts
 
 
* database upgrade script named "dbs" + new version + "from" + old version + ".sql"
 
 
* Value Script.sql
 
 
* Code Snippet.sql
 
 
Occasionally additional SQL files need to be run during update. In such cases, the files are named
 
"dbs [version number] . [sequence number] . [ etc ].zip"
 
 
=== IIS Server ===
 
 
Extract the contents of web.zip (dbs*webpub.zip) into the web application directory.
 
 
The web.zip filename is preceded by "dbs" + date + version.
 
 
Starting with version 1.03, the web.publish.config is always included in the web.zip, and extracting the zip will not accidentally delete the existing web.config file. Manually check whether there are new settings in the web.publish.config which need to be transferred to the web.config file.
 
 
== Configuration ==
 
 
=== Update Notifications ===
 
 
==== Version 0.99 through 1.01 ====
 
 
dbscript 0.99 introduces Update Notifications. This feature fetches information about new versions of dbscript from update.devio.at.
 
 
By default, the information is fetched by client-side Javascript.
 
 
You can configure the update notification behavior by setting the UpdateMode column in the Configuration table to:
 
 
* 0 ... client side fetch
 
* 1 ... server side fetch (the IIS machine needs to have connection to the Internet)
 
* -1 .. disabled
 
 
In Internet Explorer, client-side update fetch may lead to a security warning about accessing a different website from script.
 
 
To avoid the message, add update.devio.at to a zone that allows cross-domain access. See this [http://support.microsoft.com/kb/829934 MSDN KB entry] for more information.
 
 
==== Version 1.02 and higher ====
 
 
dbscript 1.02 introduces Update Notifications via JSONP. This feature fetches information about new versions of dbscript from update.devio.at.
 
 
You can configure the update notification behavior by setting the UpdateMode column in the Configuration table to:
 
 
* 1 ... enabled
 
* every other value .. disabled
 
 
dbscript 1.03 provides the new menu command "Updates" to allow the user to check for updated versions manually.
 
 
== Register License ==
 
 
 
* Start your webbrowser and navigate to the URL of your installation
 
* Start your webbrowser and navigate to the URL of your installation
 
* Login using the selected username without password
 
* Login using the selected username without password
 
* Navigate to Settings, upload you license key file
 
* Navigate to Settings, upload you license key file
 +
 +
== Upgrade ==

Please note that all contributions to dbscript Online Help may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see Project:Copyrights for details). Do not submit copyrighted work without permission!

Cancel | Editing help (opens in new window)