Does it matter wether we have 2005 or 2008 for the tool set because i have 2008 already and it installed with Visual Studio.. and i keep getting the cant connect to database error.. are there any work arounds i am missing?
SQL 2008 and Toolset
Débuté par
Extacykillz
, déc. 01 2009 02:06
Retour en haut
#2
Posté 01 décembre 2009 - 02:15
AND04
-
- Members
- 154 messages
erm my 2008 install works just fine with the toolset - so no it shouldn't matter.
#3
Posté 01 décembre 2009 - 02:19
Extacykillz
-
- Members
- 119 messages
AND04 wrote...
erm my 2008 install works just fine with the toolset - so no it shouldn't matter.
Ohh well i keep getting that error.. have any clue how to fix it.. maybe i didnt install the right client who knows SQL is very touchy it seems..
#4
Posté 01 décembre 2009 - 07:21
drkl0rd2000
-
- Members
- 41 messages
Extacykillz wrote...
who knows SQL is very touchy it seems..
And that is the reason most modding tools do not use it. I would try and uninstall and reinstall the toolset see if that helps your database error. Also do you have Windows XPsp3 or higher, seems they omitted the sp2 and lower users when designing this tool so if after reinstalling the toolset nothing changes you have 2 options
1. if you have a lower service pack for XP than 3, install SP3. If you have Vista turn around 3 times, jump up and down on one leg 5 times, spout hebrew curses at the machine and prey since vista is a hosed OS to begin with.
2. wait until the toolset update and see if that corrects the problem- what I recommend since the current release has to many problems to name. (outdated scripts, install paths that do not work for steam users, hosing saved games)
#5
Posté 02 décembre 2009 - 12:35
Extacykillz
-
- Members
- 119 messages
Ahh ok.. Well i have Windows 7 if that makes any difference
#6
Posté 02 décembre 2009 - 03:09
drkl0rd2000
-
- Members
- 41 messages
Extacykillz wrote...
Ahh ok.. Well i have Windows 7 if that makes any difference
Ahh well unfortunately the core error you speak off is directly related to SQL and is a well documented error. It is a shame they shackled such a powerful mod tool to such an unstable and tempermental piece of software as SQL, when given todays modern computer processing power it was totally unnecessary!!
Your best bet is to just wait on the new toolset version and hope they can iron out some of the critical errors. Until then put the toolset on the shelf and just play the core game!
#7
Posté 02 décembre 2009 - 08:45
discord1
-
- Members
- 1 messages
I am a data architect and I have been using it for over a decade now and the simple truth is that with any powerful platform there is going to be an increased amount of complexity, and hence an increased amount of errors, especially when dealing with inexperienced users. I have worked with MSSQL, MySQL, and Oracle and while all of them have their pros and cons MSSQL is a solid DBMS that can compete with anything on the market. 99% of the errors such as "I can't connect" involve a user mistake that is incorrectly blamed on the platform.
In this scenario the OP has already configured the DBMS environment and there might be an issue with how the toolset install expects the surface area configuration and how it has been implemented, or with a permissions issue during the toolset install or any number of other variables that may not have been taken into account by Bioware when they created the install process.
OP, what error are you getting? Can you connect to the toolset instance via MSSMS? Have you verified that you have the SQL service up and running? Have you verified that the local user you are logged in as has access to the service, if not the database? Have you checked the toolset configuration options to make sure you are looking at the correct instance - did you install to the default instance or did you create the named instance that the toolset install tries to use? Have you tried to backup and restore the DB to another instance that you do have access to?
In this scenario the OP has already configured the DBMS environment and there might be an issue with how the toolset install expects the surface area configuration and how it has been implemented, or with a permissions issue during the toolset install or any number of other variables that may not have been taken into account by Bioware when they created the install process.
OP, what error are you getting? Can you connect to the toolset instance via MSSMS? Have you verified that you have the SQL service up and running? Have you verified that the local user you are logged in as has access to the service, if not the database? Have you checked the toolset configuration options to make sure you are looking at the correct instance - did you install to the default instance or did you create the named instance that the toolset install tries to use? Have you tried to backup and restore the DB to another instance that you do have access to?
#9
Posté 08 décembre 2009 - 01:07
FalloutBoy
-
- Members
- 580 messages
Just my 2 cents, but it appears that the SQL integration is used for revision control. I do not want revision control. The only time I check anything in is when I need to delete it (because that is the only way to delete) or when I am ready to ship it.
Ideally I would prefer to see the check in and out call a custom command line, which would allow people to plug in their revision control software of choice, or opt out completely.
Ideally I would prefer to see the check in and out call a custom command line, which would allow people to plug in their revision control software of choice, or opt out completely.
