User:Allan Smith/sandbox - Revision history

Allan Smith: cleaning out the sand

2010-03-05T21:09:43Z

cleaning out the sand

Allan Smith at 23:23, 16 December 2009

2009-12-16T23:23:09Z

Allan Smith: sandbox for the configure toolset page now.

2009-12-16T21:10:40Z

sandbox for the configure toolset page now.

Allan Smith: ready for prime time

2009-12-11T23:56:37Z

ready for prime time

Allan Smith at 23:36, 11 December 2009

2009-12-11T23:36:50Z

Allan Smith at 21:57, 11 December 2009

2009-12-11T21:57:48Z

Allan Smith at 21:48, 11 December 2009

2009-12-11T21:48:22Z

Allan Smith at 21:31, 11 December 2009

2009-12-11T21:31:51Z

Allan Smith at 21:29, 11 December 2009

2009-12-11T21:29:35Z

Allan Smith at 21:18, 11 December 2009

2009-12-11T21:18:11Z

← Older revision		Revision as of 21:09, 5 March 2010
Line 1:		Line 1:
−	~~Note:If you were looking here for unable to connect issues, I have moved it all out of my sandbox into a real page located at [[Unable to connect to the database]]~~

−	~~Test edits for the configure toolset article~~
−	~~==Databases==~~
−	~~[[Image:databases window.png]]~~
−
−	~~'''Usage'''~~
−
−	~~This window is used to define the database instance that the toolset is connecting to. This window can be used to:~~
−	*Connect the toolset to the proper location if for some reason it is pointing to the wrong location and is giving the [[Unable to connect to the database]] error. If there is a valid instance of SQL server with a valid Dragon Age database in it, then you may be able to solve the problem by adjusting your configuration here.
−	*Switch between databases. If you have set up multiple instances of SQL Server or have multiple databases set up in an instance of SQL Server, you can use this utility to switch between them.
−
−	~~===Default Database Settings===~~
−	If you leave the "Use the default database" checkbox checked, the toolset will try to connect to the standard location. If your toolset is currently able to connect to the database, and you are not trying to connect it to another database, just leave this checkbox checked.
−
−	~~===Custom Database Settings===~~
−	For advanced configuration, uncheck the "Use the default database" checkbox and then click on the ellipsis button ([[Image:ellipsis.png]]) to open the data link properties window. The Data Link Properties window open. This window can be used to connect to different Servers or instances and to different databases on a selected server.
−
−	~~[[Image:Data Link Properties Window.png]]~~
−
−
−	~~You should only need to make changes on the "Connection" tab, ''only make changes on the other tabs if you know what you are doing''.~~
−
−	~~1. Select or enter a server name:~~
−
−	~~::This field shows which database you are connecting to. In a default installation, this should display .\BWDATOOLSET~~
−	::If you have done a manual installation of SQL Server, this value will likely need to be changed to .\SQLEXPRESS as that is the default on a manual installation. The dropdown list does not always populate properly, so you may just need to type in the correct entry here.
−
−	~~2. Enter information to log on to the server:~~
−
−	::Unless you changed this option while installing SQL Server manually, this field should be left as is with the "Use Windows NT Integrated Security" selected. This is the default setting when SQL is installed by the toolset, and also if you accept the defaults on a manual installation.
−
−	~~3. Select the database on the server~~
−	~~::Make sure "Select the database on the server" is checked. Select "bw_dragonage_content" from this list.~~
−
−	::''note:'' If you have created a different database, or restored your database to a different name, select or type it in this box. If you have multiple databases set up on the server, this is how you switch which one the toolset is using.
−
−	When you have finished changes on this window, press the "Test Connection" button. If you get the message "Test connection succeeded" then you should be good to carry on. Hit all the remaining "OK" and "Finish" buttons and
−	~~you should be good to go!~~

@@ Line 3: / Line 3: @@
 Test edits for the configure toolset article
 ==Databases==
-If you are having trouble connecting to the database i.e. getting the [[Cannot connect to the database]] error, you can adjust your configuration here.
+[[Image:databases window.png]]
-===Default===
+'''Usage'''
-The default database string is "<code>Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\SQLEXPRESS</code>".
-===Custom===
+This window is used to define the database instance that the toolset is connecting to.  This window can be used to:
-For advanced configuration, uncheck the "Use the default database" checkbox and then click on the ellipsis button ([[Image:ellipsis.png]]) to open the data link properties window.
+*Connect the toolset to the proper location if for some reason it is pointing to the wrong location and is giving the [[Unable to connect to the database]] error.  If there is a valid instance of SQL server with a valid Dragon Age database in it, then you may be able to solve the problem by adjusting your configuration here.

@@ Line 1: / Line 1: @@
 Note:If you were looking here for unable to connect issues, I have moved it all out of my sandbox into a real page located at [[Unable to connect to the database]]
-==Big Hammer Approach==
+===Default===
-Manual database installation works almost every time.  If it does not, it should at least should give you clues as to why it is failing, which you do not generally get when using the toolset installer.  If this "cannot connect to the database" error is frustrating you and you want to just make it work, and don't want to keep troubleshooting, this is probably your best bet:
+The default database string is "<code>Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=bw_dragonage_content;Data Source=.\SQLEXPRESS</code>".
-# '''Install the toolset without any of the database options checked'''.[[Image:Toolset setup screen.png|right]]
+===Custom===
-#:Uncheck the following both of the database settings options as shown here.  This will just install the toolset files and do nothing at all with the database itself.  Of course, since SQL Server is not installed, you would still get the "Unable to to connect to the database" error at this point.
+For advanced configuration, uncheck the "Use the default database" checkbox and then click on the ellipsis button ([[Image:ellipsis.png]]) to open the data link properties window.
-# '''Manually install SQL Server and restore the database'''
-#:It is not as hard as it may sound, and is documented [[manual database installation|here]].  Basically, when you do this, you are taking control of the two steps that you told the installer not to do, and doing them on your own.  This is effective as this way you can babysit the installation process.  Running the SQL installer this way will throw more explicit errors at you when it is having problems, making it easier to diagnose the problems and find solutions.
-−
-−
-'''Why does this work?'''
-−
-The toolset needs a database engine to run.  The installer has a copy of SQL Server 2005 embedded in it.  The idea behind this is that we could hide all the SQL Server installation, setup and administration voodoo, and do it all in the background so that you wouldn't have to figure out how to do it on your own.  When it works - it is great, when it doesn't - you land on this page...
-−
-When the toolset has finished doing its business (essentially unpacking some files and setting up some permissions and registry entries) it then runs the SQL Server 2005 installer in "silent" mode, where it just tries to install with its default settings.  The toolset installer is "blind" to what goes on during the SQL install, it just gets a message when the SQL installer says "''I'm done''", regardless of what kind of "''done''" that is.  It could be "''I just failed horribly, but I'm done failing now''" or it could be "''Whew, everything went as planned, I'm done''".  Once the toolset installer gets that message, it says "''SQL is done, so I can now restore the database''".  It then runs a command line to restore the database.  Again this process does not give proper feedback either, it just spits back another "''I'm done''" message, at which the toolset installer comes back and tells you it is finished.  Anything that goes wrong in this process will cause the dreaded error when you start the toolset.  Unfortunately there is no easy way for the installer to catch these problems and alert you.  Taking this process out of the installer's hands and running it manually allows you to see what is going wrong and react to it.  A quick internet search for any error that you get will often help you figure out what SQL Server is choking on in your particular case.

@@ Line 5: / Line 5: @@
 Manual database installation works almost every time.  If it does not, it should at least should give you clues as to why it is failing, which you do not generally get when using the toolset installer.  If this "cannot connect to the database" error is frustrating you and you want to just make it work, and don't want to keep troubleshooting, this is probably your best bet:
-# '''Install the toolset without any of the database options checked'''.
+# '''Install the toolset without any of the database options checked'''.[[Image:Toolset setup screen.png|right]]
-#:Uncheck the following options as shown here:[[Image:Toolset setup screen.png|right]]
+#:Uncheck the following both of the database settings options as shown here.  This will just install the toolset files and do nothing at all with the database itself.  Of course, since SQL Server is not installed, you would still get the "Unable to to connect to the database" error at this point.
-#:*Install MS SQL Express 2005 SP3
-#:*Restore the default database. Existing DA toolset databases will be overwritten
-#:This will just install the toolset files and do nothing at all with the database itself.  Of course, since SQL Server is not installed, you will still get the "Unable to to connect to the database" error at this point.
 # '''Manually install SQL Server and restore the database'''
-:It is not as hard as it may sound, and is documented [[manual database installation|here]].  Basically, when you do this, you are taking control of the two steps that you told the installer not to do, and doing them on your own.  This is effective as this way you can babysit the installation process.  Running the SQL installer this way will throw more explicit errors at you when it is having problems, making it easier to diagnose the problems and find solutions.
+#:It is not as hard as it may sound, and is documented [[manual database installation|here]].  Basically, when you do this, you are taking control of the two steps that you told the installer not to do, and doing them on your own.  This is effective as this way you can babysit the installation process.  Running the SQL installer this way will throw more explicit errors at you when it is having problems, making it easier to diagnose the problems and find solutions.

@@ Line 5: / Line 5: @@
 Manual database installation works almost every time.  If it does not, it should at least should give you clues as to why it is failing, which you do not generally get when using the toolset installer.  If this "cannot connect to the database" error is frustrating you and you want to just make it work, and don't want to keep troubleshooting, this is probably your best bet:
-Do a toolset, but uncheck the following options:[[Image:Toolset setup screen.png|right]]
+# '''Install the toolset without any of the database options checked'''.
-*"Install MS SQL Express 2005 SP3"
+#:Uncheck the following options as shown here:[[Image:Toolset setup screen.png|right]]
-*"Restore the default database. Existing DA toolset databases will be overwritten"
+#:*Install MS SQL Express 2005 SP3
-as shown here:
+#:*Restore the default database. Existing DA toolset databases will be overwritten
+#:This will just install the toolset files and do nothing at all with the database itself.  Of course, since SQL Server is not installed, you will still get the "Unable to to connect to the database" error at this point.
-This will just install the toolset files and do nothing at all with the database itself.  Of course, since SQL Server is not installed, you will still get the "Unable to to connect to the database" error at this point.
+# '''Manually install SQL Server and restore the database'''
+:It is not as hard as it may sound, and is documented [[manual database installation|here]].  Basically, when you do this, you are taking control of the two steps that you told the installer not to do, and doing them on your own.  This is effective as this way you can babysit the installation process.  Running the SQL installer this way will throw more explicit errors at you when it is having problems, making it easier to diagnose the problems and find solutions.
-Now, manually install SQL Server and restore the database.  It is not as hard as it may sound, and is documented [[manual database installation|here]].  Basically, when you do this, you are taking the last two big steps away from the toolset installer, and doing them on your own.  The reason that this is effective is that this way you can babysit the installation process.  Running the SQL installer this way will throw more explicit errors at you when it is having problems, making it easier to diagnose the problems and find solutions.

← Older revision		Revision as of 21:31, 11 December 2009
Line 16:		Line 16:
	'''Why does this work?'''		'''Why does this work?'''

−	The toolset needs a database engine to run. The installer has a copy of SQL Server 2005 embedded in it. When the toolset has finished doing its business (essentially unpacking some files and setting up some permissions and registry entries) it then runs the SQL Server 2005 installer in "silent" mode, where it just tries to install with its default settings. The toolset installer is "blind" to what goes on during the SQL install, it just gets a message when the SQL installer says "'''I'm''~~' done~~", regardless of what kind of "'''done'''" that is. It could be "'''I just failed horribly, but I'm done failing now'''" or it could be "'''Whew, everything went as planned, I'm done'''". Once the toolset installer gets that message, it says "'''SQL is done, so I can now restore the database'''". It then runs a command line to restore the database. Again this process does not give proper feedback either, it just spits back another "'''I'm done'''" message, at which the toolset installer comes back and tells you it is finished. Anything that goes wrong in this process will cause the dreaded error when you start the toolset. Unfortunately there is no ~~way~~ easy way for the installer to catch these problems and alert you. ~~By taking~~ this process out of the installer's hands and running it manually allows you to see what is going wrong and react to it. A quick internet search ~~using the returned~~ error will often help you figure out what SQL Server is choking on in your particular case.	+	The toolset needs a database engine to run. The installer has a copy of SQL Server 2005 embedded in it. When the toolset has finished doing its business (essentially unpacking some files and setting up some permissions and registry entries) it then runs the SQL Server 2005 installer in "silent" mode, where it just tries to install with its default settings. The toolset installer is "blind" to what goes on during the SQL install, it just gets a message when the SQL installer says "''I'm done''", regardless of what kind of "''done''" that is. It could be "''I just failed horribly, but I'm done failing now''" or it could be "''Whew, everything went as planned, I'm done''". Once the toolset installer gets that message, it says "''SQL is done, so I can now restore the database''". It then runs a command line to restore the database. Again this process does not give proper feedback either, it just spits back another "''I'm done''" message, at which the toolset installer comes back and tells you it is finished. Anything that goes wrong in this process will cause the dreaded error when you start the toolset. Unfortunately there is no easy way for the installer to catch these problems and alert you. Taking this process out of the installer's hands and running it manually allows you to see what is going wrong and react to it. A quick internet search for any error that you get will often help you figure out what SQL Server is choking on in your particular case.

@@ Line 7: / Line 7: @@
 Do a toolset install with "Install MS SQL Express 2005 SP3" unchecked, as well as "Restore the default database. Existing DA toolset databases will be overwritten" unchecked, as shown here:
-[[Image:Toolset setup screen.png]]
+[[Image:Toolset setup screen.png|center]]
 This will just install the toolset files not install, restore or configure a database at all.  Of course, since SQL Server is not installed, you will still get the "Unable to to connect to the database" error.
-Now, manually install SQL Server and restore the database.  It is not as hard as it may sound, and is documented [[manual database installation|here]].  Basically, when you do this, you are taking the last two big steps away from the toolset installer, and doing them on your own.  The reason that this is effective is that this way you can babysit the installation process.  Running the SQL installer this way will throw more explicit errors at you when it is having problems, making it easier to diagnose
+Now, manually install SQL Server and restore the database.  It is not as hard as it may sound, and is documented [[manual database installation|here]].  Basically, when you do this, you are taking the last two big steps away from the toolset installer, and doing them on your own.  The reason that this is effective is that this way you can babysit the installation process.  Running the SQL installer this way will throw more explicit errors at you when it is having problems, making it easier to diagnose the problems and find solutions.
-Background:
+'''Why does this work?'''
-The toolset needs a database engine to run.  The installer has a copy of SQL Server 2005 embedded in it.  When the toolset has finished doing its business (essentially unpacking some files and setting up some permissions for and creating necessary registry entries) it then runs the SQL Server 2005 (3rd party software)in "silent" mode, where it just tries to install with its own set of default settings.  The toolset installer is "blind" to what goes on during the SQL install, it just gets a message when the SQL installer says "I'm done", regardless of what kind of "done" that is.  It could be "I just failed horribly, but I'm done failing now" or it could be "Whew, everything went as planned, I'm done".  Once the toolset installer gets that message, it says "SQL is done, so I guess I'm done now too".

← Older revision		Revision as of 21:18, 11 December 2009
Line 8:		Line 8:

	[[Image:Toolset setup screen.png]]		[[Image:Toolset setup screen.png]]
		+
	This will just install the toolset files not install, restore or configure a database at all. Of course, since SQL Server is not installed, you will still get the "Unable to to connect to the database" error.		This will just install the toolset files not install, restore or configure a database at all. Of course, since SQL Server is not installed, you will still get the "Unable to to connect to the database" error.