Is there any way to link tables from SQL Server to Access as read-only?
There's too much data to do an import.
While providing the credentials to choose the tables from your SQL database, you can configure this SQL user to have read only permissions.
Add tables to Access database (trough Linked tables)
Set SQL user (or Windows User, or Role) to "datareader" only. (in SQL Management Studio)
Related
Our software requires the business users (of the software) to have read and write access to the database (MS SQL Server). The users are added to an active directory group with this SQL permission. The business users also want to query the database as read only in SQL Server Management Studio. Is there a way that the user can have read write access to the database from the software and read only from the back end in SQL Server Management studio?
As the SQL server permissions are assigned to the Active Directory group, the users in the group will be able to have the same permissions irrespective of from where they are accessing the database (from the software or MS SQL server management studio)
The permissions cannot be changed based on from where the users are accessing the database
We want to be able to query the Data Warehouse database from the SQL Server database both with the same server name in Azure. Select statements including the database name (e.g. select * from server.dbo.product) returns with error that a reference to the database and/or server name isn't supported in this version of SQL Server. There are articles on creating an external data source in the SQL Server database but we get error that the credentials don't have permission to perform this action.
Azure SQL (as of Azure SQL V12 in late-2016) does not support cross-database queries the same way that they do with a normal on-premises SQL Server (e.g. using the DatabaseName.schemaName.TableName syntax).
Given that Azure SQL and Azure Data Warehouse databases each reside in different physical servers it wouldn't work anyway, as the above syntax is intended for databases that all reside in the same server.
Azure SQL does support cross-database calls via the EXTERNAL DATA SOURCE feature, which we have in normal on-premises SQL Server already. This is documented here: https://azure.microsoft.com/en-us/blog/querying-remote-databases-in-azure-sql-db/
Note that performance won't be that great and you might be better-off doing the querying in your application code. For example complex JOINs which reduce data will run suboptimally.
I'm using MS Access 2013. I have a some tables which I would like to migrate to SQL Server 2012 (Management Studio). I want these tables to be used in SQL Server for addition etc., but I also want these tables to show as 'linked' in MS Access.
How do I make it so the tables look populated in MS Access, but are manipulated from SQL Server?
The Migration tool in SQL Server did not give me my desired results.
I'm not sure why you want to move it to SQL server from Access. If you say it is just for addition purposes, that is a really bad idea to move from Access.
You will need to create a shell database in SQL Server.
From Access select > External Data > More > ODBC Database and follow the prompts to export the data into SQL Server.
After that select > External Data under Import and Link > ODBC Database
This will link the local Access table to the SQL Server table and you will be able to run queries you require.
Create Database in SQL Server https://msdn.microsoft.com/en-us/library/ms186312.aspx#SSMSProcedure
Migrate Data from Access to SQL Server. For Access 2013 you will need to use the SQL Server Import and Export Wizard. Search the start menu for "Import and Export Wizard". It comes installed with SQL Server. For the data source choose Microsoft Access and follow the steps.
How do I make it so the tables look populated in MS Access, but are manipulated from SQL Server? Create a linked table via ODBC connection. https://support.office.com/en-us/article/Import-or-link-to-SQL-Server-data-a5a3b4eb-57b9-45a0-b732-77bc6089b84e
We are having some problem in server hosting SQL server 2005. We are required to take backup of all the databases and restore the same once the
window 2003 server and sql server 2005
is reinstalled.
We also need to restore all the users/groups/roles and permissions as it is which were there earlier.
Please guide the steps.
The database securables are backed up with the database.
What you will have to do is to script and recreate the logins. If the logins are SQL Server logins (not the windows logins, ie), the trick is to create them with the same SIDs as before to avoid orphaned database users (this can bi fixed manually, but it's much easier to recreate the same-SID logins).
Here's the article on MS support describing the procedure in detail:
https://support.microsoft.com/en-us/kb/918992
In the new login dialog of the SQL Server 2005 Management Studio Express, what is the User Mapping actually doing? Am I restricting access to those databases that are checked? What if I check none?
It's mapping user rights to specific databases. If you don't check any, that user won't have rights to any database unless it is in a server role that allows rights to individual databases.