I am freelancing to a game server company and this game server uses a dedicated server with SQL Server 2008 on it, the game client connect to the game server on a random port (not a problem) and the SQL Server is closed down on the dedicated server, so it can't be accessed from a external source.
I am working on an idea to sell to my manager to create a web service, so I could make an online registration form and control panel to people to manage their goods online (without the game).
Well the question is: what's the best way to make a web service (the port 80 is open and with iis7/windows server 2008) to work on SQL Server 2008 Express, providing XML with some info to my Control Panel, and to make the online form to send a request to create new players on SQL Server too and answer with a XML confirming it?
I know I could do on PHP (since this IIS7 has php installed on it), but that would be a hell of work, and if there is no other way I will be doing it manually on php.
I would like to know if there is some way to work with something like NuSoap to work with SQL Server or any other way that is not the NATIVE SQL Server, (that I just read on microsoft website that is deprecated). And how to do it if possible
Thanks in advance
Create an OData service using WCF over an EF model of your game database. Read here: Creating an OData API for StackOverflow including XML and JSON in 30 minutes
Related
I developed an app with vb.net to update a SQL Server database.
The app is connected with SQL Server in my computer and seems working very well.
But my target is to put this database in the common mass storage to be updated with this app from 20 people (20 client PC).
My questions are:
how to do to install the database in the common mass storage?
should the SQL Server Express be installed in the 20 client computers?
how to connect the app to the database (located in the common server) using ADO.net?
Thanks in advance
It really depends. If everybody is suppose to use the same data I would look at putting up a sql server that everyone can access on the network. If the data needs to be used from computers outside of a local network I would look at getting a database from a web host. For these instances you would have to update the server to your connection string to the url of the new sql server. If everyone is using there own data it is ok to use there own sql express instance.
A company I work for has an application written in VB.net with a SQL Server database storing all information. Works fine no complaints, but we also want to upload/download files within the application, and have the files + SQL Server database on a remote server i.e. working over the internet.
We could just use a VPN but that's not the best method. What would you suggest we use to communicate securely between the application and the remote server for both the database and filesharing?
I was thinking of doing everything over HTTPS, but we would need some kind of agent on the other end to receive requests.
Sorry if this is a noob question, I have no experience with VB.net myself, I usually use PHP + C!
Thanks
Use a VPN. It implies just deployment and configuration.
'Going over HTTPS' means you rewrite your application, as the current VB app is expecting T-SQL and SMB endpoints to discuss with.
I'm newbie for Amazon EC2.
I'm given an assignment where I've to connect VS 2008 to Sql Express 2005.
VS and Sql Express are running on separate Amazon machine.
(I mean, I've to do 2 separate Remote Desktop Connection to access both).
I've no clue how to connect to the Sql Express.
I've been trying different options found in search on google, stackoverflow etc...
But no luck.
Any help is appreciated.
Assuming that you have a connection string (to server ec-xxxxxxx.xxx.amazon.com), your problem could be that the .Net instance (let's call it NET) and the SQL Server instance (SQL) don't have the rights to see each other.
Create two instances with the different security groups
On both groups, you'll like want to open RDP (you probably have that already as I can read)
On the SQL instance security group create an inbound rule for port 1433 and open it only for the security group of WEB. Otherwise, the whole world can access your SQL Server Express database. Like this, only the WEB instance can access it. You need to paste the security group id of WEB into the inbound rule for SQL to do that.
Good luck.
In our development team we have:
4 developers
one application uses PHP and database Microsoft SQL Server 2008r2, except one using PowerBuilder instead of PHP and one using MySql instead of Microsoft SQL Server
All applications are database-centered, some of them are for general public, some are not.
Question is: for the procedures and functions shared by all applications, what does it make most sense to use, database procedures/functions or web services?
We could not find an agreement within the team.
Whatever you answer, please explain the reasons.
Webservices and Database Proc/Functions are two entirely different things.
Webservices are the services over the web, mainly used when a client and a server interact and client interacts with the server through web or HTTP or any other protocol.
Database proc/func - are created to interact with a login to a DB server.
In your case, if all the application are in the same domain... then you dont need to access through webservices and also it is a lot of overhead.
You can create a common DB server , where you can keep these proc/func and can be consumed by all.
I've been developing a site using ASP.NET MVC, and have decided to use the new SQL Server 2008 FILESTREAM facility to store files 'within' the database rather than as separate entities. While initially working within VS2008 (using a trusted connection to the database), everything was fine and dandy. Issues arose, however, when I shifted the site to IIS7 and changed over to SQL authentication on the database.
It seems that streaming a FILESTREAM doesn't work with SQL authentication, only with Windows authentication. Given this, what is the best practice to follow?
Is there a way to force this sort of thing to work under SQL authentication?
Should I add NETWORK SERVICE as a database user and then use Trusted authentication?
Should I create another user, and run both the IIS site and the database connection under this?
Any other suggestions?
Take a look at this article. I don't know a whole lot about FileStreaming and security, but there are a couple of interesting options in the FileStreaming setup such as allowing remote connections and allow remote clients to access FileStreaming