I want to rent a dedicated Server for my company with the newest Microsoft SQL-Server on it and I want to use filestream to store some PDF Files within the SQL Server. I have read "Windows only" on the official Microsoft site and I am wondering if this means that the Server musnt run on a Linux Server or does this mean that the SQL Server needs to run on a local Windows machine and not Windows Server?
I just want to confirm my initial conclusion that the server I want to rent must be a Windows Server Running-SQL Server on it since I am not completely sure how this works, I have never done this.
Related
I have the server
DESKTOP-TI7M67V\SQLEXPRESS (SQL Server 12.0.2269 - DESKTOP-TI7M67V\joe)
It is a SQL Server 2014 database engine using Windows authentication.
I need to create a new server, database engine with SQL Server authentication this time, that I need to connect and view into the same SQL Server Management Studio instance I use for my server by now, since I need to create queries involving both.
I've seen that I can do it with linked server feature, but I need to create and setup the new server correctly.
The access to this new server, obtainable through SQL Server authentication, must have different authentication parameters than the other one already existing, if a user doesn't have them, he would be able to access the old server, but not the new. The access of both servers has to happen in the same SQL Server Management Studio instance.
Plus, the databases files of this new server must be portable. For portable, I mean that all its files (that make it work) must be able to be put in a custom directory on two pcs, with SQL Server 2014 already installed on both, and be copyable and pastable, e.g on a pendrive, in order to be transferred from a PC to the other. That's for maintain synchronization between two different physical users workplaces in which the database will be used, workplaces that for the moment are not directly interfaceable with a single, fixed, detached and interconnected source on which place the database.
My question is how to create a new server that would have these features.
I'm doing the SSRS setup in my DEV environment. I've been using (LocalDb)\MSSQLLocalDB for some of my databases. Now that I want to start using SSRS, can I use (LocalDb)\MSSQLLocalDB as a data source for SSRS? I already tried, but I'm not able to connect it. However, if I use the server name (name of my computer) it works.
Do I have to use the actual server name? Is local database (LocalDb)\MSSQLLocalDB a wrong way of doing it? I'm assuming that the actual server name will be the best practice.
If I have to use the server name, that means that I will need to migrate my databases from (LocalDb)\MSSQLLocalDB to the instance of the server name.
What do you recommend?
LocalDb instances run in your desktop session, and are meant for desktop applications (particularly Visual Studio). So no. You should migrate your databases to a service-based SQL Server instance for SSRS (which runs as a Windows Service) to access them.
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).
This is my first time using it, I come from a PHP/MYSQL background and a client is asking me to assist with his MSSQL database and he gave me a file which is the exported database, it doesn't have an extension though.
I downloaded and installed Microsoft SQL Server Management studio but I'm not sure what to do, the tutorials online seem to be able to connect to the local server, on my end when I browse for a Server name I can't find anything under "Local server".
If it helps, the client have informed me that his previous developer (the one who seems to have had a conflict with the client and left) was using the same application with the server type set to "Database engine" and the Authentication set to "Windows Authentication", that's all the information I have.
Please help. Thanks.
If you installed a default instance of SQL Server with Management Studio, use the server name "localhost". If you only installed SQL Server Management Studio, you will need to at least download SQL Express: http://www.microsoft.com/en-us/server-cloud/products/sql-server-editions/sql-server-express.aspx
Also, note that if you develop in the latest version of SQL Server, you will not be able to back up and restore to the client's database if the client uses an older version. You will need to ensure all changes are scripted or use dacpacs (which you probably won't use).
I want to deploy my SQL Server 2008 Database with application on the client's machine, where i don't want that anybody can open and read or copy my Database Objects (i.e. Tables, SPs, Functions, Views etc.).
I want to protect database with password same like Microsoft Access 2007 When somebody opens it asks Password. Can it be done in SQL Server 2008, if yes how.?
SQL Server is not like Access and doesn't have any file-based password-protection mechanisms (in the "normal" editions like Web, Standard, Enterprise/Developer, Express).
SQL Server is a server-based product - you need to restrict physical access to the server the files are located on, and prevent unauthorized users from accessing the files through the SQL Server mechanisms (like logins and permissions).
If you need something like Access' password-protected files, you need to use SQL Server Compact Edition which is file-based and has a password-protect feature
An alternative approach that you may also wish to consider, that is in addition to deploying an initial secure instance configuration, is the Transparent Data Encryption feature in SQL Server. This way were someone able to access the database data files "outside" of SQL Server, i.e. via the file system, they would not be able to review the data without decrypting the data files.