View previous topic :: View next topic |
Author |
Message |
Gryphyn
Joined: 20 Jan 2005 Posts: 431
|
Posted: Sat Jul 14, 2007 7:09 Post subject: SQLServer 106.108.0.9 (CTP) |
|
|
Get it here
Cheers
Gryphyn |
|
Back to top |
|
|
Gryphyn
Joined: 20 Jan 2005 Posts: 431
|
Posted: Sat Jul 14, 2007 13:47 Post subject: |
|
|
Two for the price of one...
Just double checked after Papillon's news (1.08 final) and everything still works as expected.
Cheers
Gryphyn |
|
Back to top |
|
|
Papillon x-man
Joined: 28 Dec 2004 Posts: 1060 Location: Germany
|
Posted: Sat Jul 14, 2007 15:30 Post subject: |
|
|
Good job!
I have to admit I'd probably use SQL Server Express for my own PW nowadays. The main reason behind this is that I work with it professionally, so I know more about it than e.g. MySQL. It also uses more resources, but the actual difference might be negligible, especially on dual core processors.
The tools that come with SQL Server (e.g. Profiler and Database Tuning Wizard) are another reason why I'd consider it.
And of course, it's free. _________________ Papillon |
|
Back to top |
|
|
Gryphyn
Joined: 20 Jan 2005 Posts: 431
|
Posted: Sun Jul 15, 2007 2:34 Post subject: |
|
|
It's also a means to allow C# coding via this plugin.
(the plugin can be used as a bridge)
By writing a CLR Stored Procedure, and adding it to your database, you get an entry point to do pretty-much anything (Database related, or not)
This is where I intend to take the plugin (at least for my needs). I can squeeze a little better performance with a C# procedure.
-- AND
ODBC support is only a 'Driver' away.
The plugin uses the ODBC API, and exposes the 'core' directly into your NWScript. (You can read the ODBC documentation to get an idea what each function does)
Cheers
Gryphyn |
|
Back to top |
|
|
Balo
Joined: 12 May 2007 Posts: 4
|
Posted: Sat Aug 11, 2007 19:06 Post subject: |
|
|
I'm trying to set this up. I've been running nwnx4 with mysql, but i'd like to get it on sql server.
I'm running a default instance of sql2005 (not sqlexpress). I can't seem to get the hook into the database to work.
I keep getting
* Loading plugin xp_sqlserver.dll: Error 14001. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
For my instance in the xp_sqlserver.ini file, I've tried each of the following and none have worked. The app isn't failing authentication, it's just not finding the server at all.
instance = .\MSSQLSERVER
instance = .
instance = [Server name]\MSSQLSERVER
instance = [Server name]
Any thoughts on how to get this to connect to a default sql2005 instance? |
|
Back to top |
|
|
Balo
Joined: 12 May 2007 Posts: 4
|
Posted: Sat Aug 11, 2007 21:08 Post subject: |
|
|
I guess my problem is more fundamental than that. I'm running nwnx4 1.08, and I've tried reinstalling it again, in hopes maybe something was missing version-wise.
I created an alias to SQL named .\SQLEXPRESS and verified via several tools that I can hit my instance using that name. Then tried again but xp_sqlserver.dll just wont load. Same error. I can get xp_mysql.dll to work fine.
If anyone has thoughts, I'd appreciate a hand. I'd love to get my nwn2 server on sql. |
|
Back to top |
|
|
Papillon x-man
Joined: 28 Dec 2004 Posts: 1060 Location: Germany
|
Posted: Thu Aug 16, 2007 22:57 Post subject: |
|
|
Balo wrote: | * Loading plugin xp_sqlserver.dll: Error 14001. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
|
This points to a missing DLL. The plugin is not even beeing loaded, so any other attempt will be futile as well.
Gryphyn, what might he be missing ? _________________ Papillon |
|
Back to top |
|
|
Gryphyn
Joined: 20 Jan 2005 Posts: 431
|
Posted: Fri Aug 17, 2007 1:26 Post subject: |
|
|
Papillon wrote: | Balo wrote: | * Loading plugin xp_sqlserver.dll: Error 14001. This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem.
|
This points to a missing DLL. The plugin is not even beeing loaded, so any other attempt will be futile as well.
Gryphyn, what might he be missing ? |
OK, Not sure on this.
Sorry I missed your earlier post Balo. Didn't appear as unread.
Tonight (+8hrs), I'll rebuild & x2 check it.
I'll keep you posted.
Cheers
Gryphyn |
|
Back to top |
|
|
Gryphyn
Joined: 20 Jan 2005 Posts: 431
|
Posted: Fri Aug 17, 2007 2:02 Post subject: |
|
|
Quote: | I created an alias to SQL named .\SQLEXPRESS |
Not exactly sure what you mean by this.
If you install SQLServer(Express) ".\SQLEXPRESS" is the Instance name you get by default. (it might look more like "<YOURPCNAME>\SQLEXPRESS")
If you are using SQLServer 2005 you need to change this to
<YOURPCNAME> for an unnamed(default) Instance, or add "\<INSTANCENAME>" for a named instance.
**Anything in <> should NOT be taken literally.
To help when you connect using the Studio whatever appears as "Server name:" is what you need.
--Reread your post.
instance = . should have worked (?)
try
instance = (local) --or
instance = <PCNAME> --your computers name.
you ran the .sql script? This will create the database for you.
--if you change the database in this script you need to add the line
database = <new name>
in the .ini file.
Just a reminder. This version WILL NOT run your existing MySQL scripts.
Not only is the SQL different, but the NWScript commands are different.
(the next version will have NWScript commands aligned)
--The demo mod is the place to start.
if the .ini file has no username/password details. Windows authentication will be used.
Cheers
Gryphyn |
|
Back to top |
|
|
Gryphyn
Joined: 20 Jan 2005 Posts: 431
|
Posted: Fri Aug 17, 2007 3:56 Post subject: |
|
|
Could also be the service pack issue.
vcredist_x86.exe may help.
Cheers
Gryphyn |
|
Back to top |
|
|
Balo
Joined: 12 May 2007 Posts: 4
|
Posted: Sat Aug 18, 2007 2:32 Post subject: |
|
|
Gryphyn wrote: | Quote: | I created an alias to SQL named .\SQLEXPRESS |
Not exactly sure what you mean by this.
If you install SQLServer(Express) ".\SQLEXPRESS" is the Instance name you get by default. (it might look more like "<YOURPCNAME>\SQLEXPRESS")
If you are using SQLServer 2005 you need to change this to
<YOURPCNAME> for an unnamed(default) Instance, or add "\<INSTANCENAME>" for a named instance.
**Anything in <> should NOT be taken literally.
To help when you connect using the Studio whatever appears as "Server name:" is what you need.
--Reread your post.
instance = . should have worked (?)
try
instance = (local) --or
instance = <PCNAME> --your computers name.
you ran the .sql script? This will create the database for you.
--if you change the database in this script you need to add the line
database = <new name>
in the .ini file.
Just a reminder. This version WILL NOT run your existing MySQL scripts.
Not only is the SQL different, but the NWScript commands are different.
(the next version will have NWScript commands aligned)
--The demo mod is the place to start.
if the .ini file has no username/password details. Windows authentication will be used.
Cheers
Gryphyn |
Thanks for the response Gryphyn.
An alias is created through the SQL Server Configuration Manager, and is similar to a DNS alias, but for SQL. It just redirects a nickname to a real server name. It was just a last ditch effort.
I hoped that just using the servername would have worked, but it didn't even try to connect. I did install the .sql script and changed the db name as appropriate. But as stated, based on all auditing including running a SQL profiler trace, an attempt to connect to the database engine isn't even made.
I'll try out the service pack for visual C++ you mentioned below and see if it will work. |
|
Back to top |
|
|
Gryphyn
Joined: 20 Jan 2005 Posts: 431
|
Posted: Mon Aug 20, 2007 4:01 Post subject: |
|
|
Balo wrote: |
Thanks for the response Gryphyn.
An alias is created through the SQL Server Configuration Manager, and is similar to a DNS alias, but for SQL. It just redirects a nickname to a real server name. It was just a last ditch effort.
I hoped that just using the servername would have worked, but it didn't even try to connect. I did install the .sql script and changed the db name as appropriate. But as stated, based on all auditing including running a SQL profiler trace, an attempt to connect to the database engine isn't even made.
I'll try out the service pack for visual C++ you mentioned below and see if it will work. |
Mwahhahaha!
Just took your 'Alias' advice and applied it to our $1000-a-seat SQLServer product. Brought it to a screaming halt - literally. (and this is the one that just went out the door - whoops! )
Needless to say no-one likes me around the office at the moment
*no-one likes a smart-arse*
Thanks!
Most fun I've had around the office for a long time
Cheers
Gryphyn |
|
Back to top |
|
|
Papillon x-man
Joined: 28 Dec 2004 Posts: 1060 Location: Germany
|
Posted: Tue Sep 04, 2007 22:31 Post subject: |
|
|
Heh, good job, Gryphyn
After reading through the current posts, I think your Visual Studio or your copy of wxWidgets from the NWNX4 repository might be on SP1. The repository is being updated right now, so you might want to recompile. _________________ Papillon |
|
Back to top |
|
|
Gryphyn
Joined: 20 Jan 2005 Posts: 431
|
Posted: Wed Sep 05, 2007 0:12 Post subject: |
|
|
Papillon wrote: | Heh, good job, Gryphyn
After reading through the current posts, I think your Visual Studio or your copy of wxWidgets from the NWNX4 repository might be on SP1. The repository is being updated right now, so you might want to recompile. |
Yep, The major issue is the VS-SP1 stuff. It's one of those things where I need to balance C# & C++ development (C# is winning atm).
My wxWidgets, SQLite are the most recent versions, so your code is just catching up
PS. did you get the "realtime" plugin options into the time plugin?
If not I'll get someone to recompile "realtime" and have it as a separate plugin
Cheers
Gryphyn |
|
Back to top |
|
|
Papillon x-man
Joined: 28 Dec 2004 Posts: 1060 Location: Germany
|
Posted: Wed Sep 05, 2007 18:44 Post subject: |
|
|
Gryphyn wrote: | My wxWidgets, SQLite are the most recent versions, so your code is just catching up |
What I meant was: The binary libraries of wxWidgets in the repository where compiled with SP1, the comment was not about the wxWidgets version itself.
Gryphyn wrote: | PS. did you get the "realtime" plugin options into the time plugin?
If not I'll get someone to recompile "realtime" and have it as a separate plugin
|
No not yet, but this is something for the next release. _________________ Papillon |
|
Back to top |
|
|
|