I need some help.
When we install the Database at the clients end, the client can see all
the SQL tables, views and stored procedure in the Enterprise Manager.
Is there a way via which you can restrict the client from viewing the
tables in SQL Enterprise manager?
I hope you understand my question.
I would be oblidged if my friends could help me...
Is there any way of not allowing users with MS Access from using it to connect to a SQL 7 server? Basically, no connection to SQL through MS Access should be allowed. Any ideas?
My users have sa rights to our SQL servers. I want to restrict their access to the C: so that they do not restore DB's there.
I thought at first I could create a Windows user that runs the SQL Service then grant them read rights to the C:. This does not give the user enough rights to start the service.
My users have sa rights to our SQL servers. I want to restrict their access to the C: so that they do not restore DB's there.
I thought I could create a Windows user that runs the SQL Service then grant them read rights to the C:. This does not give the user enough rights to start the service.
In SQL2005, is it possible to restrict incoming sql or windows authentication logins by source hostname or IP address? Perhaps using endpoints?
We are currently using hosts file on the db server as a temporary solution, but the SA will not allow us to use this as a permanent solution.
The app team I support is asking me to build an "idiot proof" database so that an Dev or Test app server they may configure, doesn't unintentionally connect to the Production database and damage/alter data.
Don't worry, I've already asked if they can't follow some kind of M&P's to prevent this kind of silly behavior, but they insist on DBA team creating a bullet-proof database that can outsmart app developers who try to attempt something dumb like this.
Any ideas or suggestions would be greatly appreciated.
2. Encrypt contents of the whole database. Is there anything available in SQL Server 2005 (server or DB settings) which encrypt the contents. I do not want to explicitly encrypt individual columns !!
We have a situation where we need to restrict access to a sql server data file. That is, to prevent users viewing any tables, stored procedures, etc, in sql server or another tool. We are providing a our database as part of an application install to a customer's site which will run isolated on the customers network. However the application will have sql server logins and the system must still be able to execute stored procedures.
The setup unfortunately cannot be changed and we are trying to think of best implementations for this. Our customers are also working with competitors so we are very conscious about exposing our data structures to anyone outside of our company, hence trying to restrict access. If deployed to a sql instance on the customer site then they will have database administrator accounts on the server.
I have few SQL user who has permissions on different databases. When they are accessing MSSQL server from Enterprise Manager they can see all Databases but can not access them and they can change file size allocated to them. I want to restrict this and they can only see database belongs to respective user and restrict user to change allocated size. Please help me with this as I am not able to find the solution.
I have added several Active Directory groups and set the system roles for each to "System User" and set one of the groups (DBAdmin) to "System Adminstrator"
My issue is that even after doing this, the users in the other groups are able to access the "Configure site-wide security" link under Security and change the permissions. The only system permission these users have is "View shared schedules" so it doesn't seem that this should be possible.
I would appreciate any feedback on this issue. Thanks!
I have a single database and 5 user which use this database for DDL and DML operations.
The problem we are facing here is, every time a user need to do some work in this database he/she had to ask(manually) to rest of the 4 users whether they are doing some task over the same DB or not. Sometime due to communication gap one user open any transaction which creates a deadlock for another user to execute any query over the same tables in this DBI want to get rid of this problem by making it configurable from SQL Server part so that if any user which is already accessing this DB, so the other user don't get access to it, kind of Mutually exclusive behavior.
I'm looking to deploy some SQL Server reports and I want to restrict the access that the users have. Currently when connecting to the reports site they have access to a lot of functionality through the header bar, for example - Properties - New Folder - New Data Source - My Subscriptions - Site Settings - Search etc.
How can I disbale or hide all these options so that all the user sees is the list of reports?
Hello AllI am using SQL server 2000 as the backend of my application but don'twant my clients tobe able to view or edit the database tables, storedprocedures , view etc using enterprise manager or query analyser (orsimilar tools)How can this be done ?I searched a lot for this but unable to get the correct answer isthere anybody to give full solution regarding this.Please relpy me as early as possible
I have two databases DB1 and DB2 DB1 has a source table named 'Source' I have created a login 'Test_user' in DB2 with Public access. I have also created a view named 'Test_view' in DB2 which references data from DB1.dbo.Source
I have two databases DB1 and DB2 DB1 has a source table named 'Source' I have created a login 'Test_user' in DB2 with Public access. I have also created a view named 'Test_view' in DB2 which references data from DB1.dbo.Source
I am setting up the SQL2005 reporting service to let users build their own reports on the web. I'll provide them with pre-built report models. We have concern with SQL database performance by allowing users to execute huge reports. The problem that I have is: If I give the users permissions to build report they'll have access to the report's Properties | Execution page, which allows them to disable the report execution timeout. Is there a way for me to allow them build reports while restrict them to access the report execution timeout settings?
My department has some questions about Client Access Lisences. Specifcally, they want a definition of what does and does not require a CAL, and they want something somewhat official. I checked the MSKB, and looked on their sales website, but all I can find is the EULA, and that doesn't help me all that much.
I am experiencing VERY slow connectivity between client and server SQL 2000. I have checked the network activity and it is low. It also takes Enterprise manager ages to load, and then browsing tables and trees is impossible!
I recently made a DTS-package from importing external data in my sql2k server. I linked my access file to the sql server to make some reports.
Right now, my clients run the dtsrun utility through a batch file themselves. I gave them permissions to be the dbase owner.
Now when you link from access to sql server as admin, your names are : dbo_Tablename. If it's another user, the names get pvanmoer_Tablename and for another user it's cvanho_Tablename. (Validation through NT) So my linked tablenames aren't valid anymore in my access file. So I need to relink them each time.
How can I avoid this problem ? I've been trying to create tables without dbaseowner, but this doesn't seem to work.
Is there a way to update data on a MS Access 2000 client from SQL Server without polling a table using the form's onTimer event?
It would be much more elegant if I could push the data to the clients every 15-30 minutes when the data on SQL Server gets refreshed.
Can DTS do this? The forms I'm talking about are select only, no editing.
I know I can do this with java and multicasting, should work with MM Flash as well with listeners. I would really like to take this app to Flash, but we have a 1 month timeline to port from Access to SQL Server.
Hi, We're *very* new to using SQL Server and are just getting it up and running. We're only running simple queries right now, but we're doing so by connecting to our server via 'Remote Desktop' to run the management studio to run the queries.
Is there an SQL client that can be installed on a user's workstation that will allow them to run queries without having to use a 'Remote Desktop' connection on the server?
I want to give a client access to a SQL Server 7 database sitting on a different NT domain without setting up a trust relationship between the two domains. Has anyone tried doing this?
I'm thinking to upgrade SQL6.5 DB to SQL 2000 but do not know all client access with SQL 6.5 utility will work ??? (The application is a vendor canned package using SQL 7.0 DB but client can access with 6.5 ---Not using ODBC) Any experts can help ? Thank you in advance !!
The reason I want to put an ip address on connection string i just want to create connection strings as people do in their work. When the app tried access the connection string it gives the error in the attachment.
Because I haven't used this user/password for a long time I'm pretty sure the user name and password is correct but i have the following questions
1. Assume the user and password is incorrect, is there way to reset this? 2. what other configuration that i need to do in order to make teh C# app access this Database?
I have an excel workbook, that has a pivot table in it where the data source is an OLAP cube. My problem occurs on the client machine, logged in as the client. I remote into the PC, and create a pivot table using the OLAP cube connection. I create the pivot table and everything works fine - I am able to browse the data with no issues. Once I exit the Excel Workbook, and come back in - I am no longer able to connect to the datasource. I have tried both saving the password in the connection and not saving it. It has made no difference.
If I give the user access dbo on 1 of the database, when he logon using SQL Server Management Studio for running query etc, can he only see his database instead of other as well system database?
Is there any best practise in term of setting the SQL client for 2005?
I am writing a Windows Application which will be used by about 100 clients. (NT Authenticated)
The application is going to be used in a LAN enviroment. User who have access will download a VB.NET application from a web site.
Of course, I want to prevent any of the 100 users from using a tool such as Query Analysis or ODBC to connect directly to the database and modify data.
So, it appears the way to go is to the "Application Roles". For this to work, the application roll password has to be saved in the application to execute the sp_setapprole procedure.
Is there a way to secure this password? I am worried about a user somehow extracting the password from the application and connecting directly.
Am I on the right track here? Any ideas appreciated!
I have SQL Server 2005 installed and functioning (it does everything I've asked it to do locally). I also have the Express and Standard Editions installed on a computer running WinXPPro SP2 with all the WinUpdates applied. I also have VS2005 installed on this computer. I've done some development work on this computer, using VS2005 to create a SQLDB, connect to it, add data, etc. This is all okay.
The problem is I cannot connect to the SQL Server from the client computer. I installed the client tools on this XP Pro box along with all the WinUpdates. Here's what I can do...
I can ping the SQL Server by name (the name gets resolved). I can copy files between the two computers using Explorer. I enabled "Allow remote connections to this server" in the Server Properties / Connections page. I did not change the default port of 1433. The TCP/IP protocal is enabled in the Configuration Manager. The Surface Area has been configured to allow local and remote connections using TCP/IP and named pipes. SQLBrowser surface is running as is the MSSQLSERVER service.
So what's going on? I am new to SQL Server to it may be something very simple / obvious.
I work at a place that does device testing where the test results are saved in a SQL database. I have an objective to create a plan for a pilot project to place the data on our intranet so our engineering dept can research test results.
I'm trying to find some group I can beg / borrow / pay to look at our schema and help me chart out what tools we should use and how much (ballpark) work is involved.
I'm a VB.NET developer. I did a tutorial on SQL Reporting Services and see potential there. I skimmed a tutorial on SQL Analysis services, and like the idea of being able to trend our data. But it's over my head at this point to get from where I'd like to be to what Microsoft tools to use and how to put them together.
I contacted one local DB/Developer shop and they wanted to bring in a team of engineers for two days and charge us $6000 for a "total solution". Instead of that, I'd like to maybe spend an hour on the phone and some emails to send a schema to someone who knew the tools inside/out and get a pretty good recommendation for a reasonable price.
I am a VB6 programmer and I'm really new to SQL Express, I have always used ACCESS because it was so easy to deploy. I've now written a VB6 program which uses SQL Express and I want to know how to deploy it. Basically my PC will host the SQL database as it has SQL Express loaded onto it. I now want to install my EXE onto other Client's PC and have them read/write to the database on my machine.
Besides the EXE program, what software do I need to load onto the Client's PC so they can access my SQLExpress database...? (eg: Net Framework, SQLExpress, etc).
Also, if my machine is called ABC123, in my connectionstring do I just put in
ABC123sqlexpress as the datasource..?. Will this be enough for the other PCs to connect to mine ?
we have a sql express - that comes standard with servers.I just wanted to know.....Is there any addition Client access licenses needed for this sql express or not.