I have a software that accesses a SQL database in the cloud. The SQL installation must be done on the client pc or my program already can access it regardless?
Your client only needs OLE DB Provider or an ODBC driver. Since your using SQL Sever, you can use the SQL Sever Native Client. More information and downloads can be found here.
Usually you don't install SQL Server or other large RDBMS on the client. Usually this is accessed via Intranet (or less frequently over internet).
You will need to tell us more details.
Related
I have a QNAP nas and I want to give my SQL Server 2019 access to a share on the server. The NAS is linux based and not part of a domain.
I simply want to give my SQL server credentials to use when connecting to that share.
How can I do this?
I'm thinking it might be a proxy but I've never set one up before.
Background: My stored procedures retrieves file details on the server.
(this should be comment, not answer, but don't have enough points) Can you access the OS on the NAS? If so this wouldn't be set up with SQL Server Proxy but as a windows folder linked to the linux share (setup with samba or similar). Then ensure the service account that SQL Server is running under has access to the windows folder (that's really linked to your linux nas). Your NAS provider might already have this functionality built in, might want to check with them.
What is the goal of the SQL Server 2019 accessing the linux folder? for backups? You probably already know but SQL Server 2019 installs on linux quite easily. I've installed on debian, centOS and amazon linux without issue.
I have been supporting a product written in VB6 with an Access database for a long time. In many of the installations a mapped drive was used to allow multiple workstations to run simultaneously. Since it seems Microsoft has broken that recently, I need to re-write everything with a new set of tools.
I plan to use VB.net and I would like to use a SQL database this time for the stability. The problem is that the market I sell to cannot / will not support installing full blown SQL Server and all the complexities of managing it.
What I am not able to find any current info about is whether or not SQL Server Compact still exists, whether or not it can be added to a NON web based project and if it will be easy to deploy and be easy to manage like an Access database was.
When I try to follow the directions to add SQL Server Compact to my project, it isn't available in the Data Source drop down list (there are "Simple by ErikEJ" versions listed but they don't seem to work) I have seen SQL Server Compact talked about with regards to web projects but I am building a locally installed .exe. I can't find ANY current info about what flavors of SQL are available right now to add to a local program running over a peer to peer network.
SQL Server Compact is no longer supported and developed by Microsoft, I suggest that you use SQL Server Express, it allows remote connections (if configured to allow it) and has modest resource requirements. Supports a database up to 10 GB of size.
As suggested, SQL Server CE can still be used but is no longer supported. For file-based databases, Microsoft currently recommend SQLite.
For a multi-user system, SQL Server Express is probably your best bet. It's still server-based though, so the server needs to be installed somewhere. For local databases, you can install on the same machine as the application and attach a data file on demand. For multiple clients, you'll need the server installed on a machine accessible to all and a permanently-attached database.
We have an application called IpSwitch Whatsup and it's installed in a machine that I can connect to remotely as administrator. This is all in our intranet.
We need to connect to the sql server database being used by IpSwitch Whatsup, but this particular machine doesn't have sql server installed. On the other hand, in sql server configuration manager there is indeed a sql server installation for whatsup (the entry says SQL Server (WHATSUP)).
So, two questions:
How does one go about in connecting to this database? I'm pretty sure I know the name of the database and I already know the server name and instance, so I would like to connect to this DB from a sql server installation in another machine.
How does one configure a sql server installation to receive remote connections if it doesn't have sql server installed?
Thanks.
For the first question, you just type in (or browse) the appropriate instance name and authentication options using SSMS - which is the GUI tool used to manage sql server instances. Note - the term "sql server installation" can mean different things so it is not a useful reference.
As for the second question, review the information here. Note that any task you do in SSMS can be done via tsql - you can see the appropriate commands using the script button in the SSMS dialog windows.
And you can also (and probably should based on these questions) install SSMS on the same machine as your server instance so you can do "anything" "anywhere". Now would probably be a good time to review your disaster recovery options (and start backing up your databases regularly).
I'm trying to set up an SQL server for my web-server to send and receive data from. I'm somewhat confused on how the whole SQL server thing works though. I was wondering why I need a separate server for my SQL and my web server. why can't I save an SQL database on the server itself instead and access it the same way one would read and write an XML or JSON file on the server to store data?
You may be getting caught up with server, as in the computer its running on (physical box, virtual machine, might be easier to think of it as the operating system) vs the server, as in web server/sql server which are different software packages.
So the SQL server (software) and the Web server (software) can run on the same server (hardware, essentially).
Depending on your use case its usually best to have the SQL server on a different server (hardware) to your web server so that there is more dedicated resources for their processes, but its not required.
If you are asking why you cant talk to the database file directly, (in the case of MS SQL Server, at least) the server manages its own permissions and manages all the file IO for you. Its a bit more complicated than a JSON file.
When writing an application that'll work with MS SQL database all we do is just we specify the connection parameters (either hard coded or dynamically). And when we install that application on a machine, we don't care if that machine has the proper tool to make the connection to the MS SQL Server database available.
However, in Oracle things are different. We have to make sure that all the machines that we want to install the app has Oracle Client set up. It will not work otherwise. Now my first question is what advantage does this provide? And the second one is if there's some way to achieve the similar in SQL Server?
Realistically, if Oracle owned Windows, the Oracle client would be installed with Windows and the SQL Server client would be a separate install. It's not a matter of advantages and disadvantages, it's a matter of who owns the stack and can bundle their software with the operating system.
Depending on exactly how you are building your Oracle application, there is a good chance that you can use the Oracle Instant Client or the Oracle thin (type 4) JDBC driver to provide connectivity to the database. Either of these can be installed by your application without requiring a separate Oracle client install.