Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
zxkelxz
Starting Member
3 Posts |
 Posted - 2010-10-13 : 16:56:14
|
| What comes first, the chicken or the egg? But really we have an installer that sets up a database by calling a script. However I have very limited knowlege on SQL programming or even setting up SQL 2005. I've purchased a book and I'm reading it but we need to move forward on this project at the same time. My question is this, if a script is called from the installer to set up the database, the actual SQL Server already needs to be running and have a name because all the script can possibly do is populate it with a database? The reasoning behind this question is a huge lack of knowlege about SQL and also ones the installer reaches the point of wanting to create the database it calls command, calls/inputs osql.exe -u sa -p*** -d master (and since we reimaged the drive we have forgotton what the last -(WhateverLetterItWas) but it had a call to a temp.sql file in its directory, ones the call is made it goes dorment for a minute and an error pops up from the installer. This error is an exception thrown within the installer and from looking at the source code we have without a doubt managed to set SQL up wrong with it already having a database to populate it with.We think some batch files are missing, from the company that supplied the source code and server images, but have access to all original imaged drives.....that yes you would know can't be started because we dont have any information about the original equipment. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
zxkelxz
Starting Member
3 Posts |
Posted - 2010-10-13 : 19:17:48
|
| Yes all the installer does is make a call to the OSQL, from viewing the code and actually getting it up to this working point. The fall out of this is, and what we cannot for the life of us figure out is the password, being that the one thats hard coded would be way to long for just 3 char *** to appear beside -P in command line(Maybe the coders were changing the pass for better strength? Never got to finish?). But also with the knowlege that the installer doesnt install SQL Server 2005 is just not logical(this program needed to go and be on any pc that it was needed), but then again this program was never finished and where just trying to salvage what we can. One thing though in the script, since we have the database, at attempted longon ones we find out what script is being called(its calling out to plenty of stuff just not in ordered fashion its being executed) would we be able to view the password in the script file? Or does SQL encrypt any -P call? That way we bypass not having to rewrite a script that interfaces with SQL(we know nothing about creating a database from a script..) and just changed the Password to that in the source code.Just want to say also thanks for your help, twice now. Our problem is just a lack of SQL knowledge and that this thing didn't come with a user manual or quotated work...its like putting the puzzle pieces together without the box. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
|
|
SQL 2005 Issue