Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 8 years ago.
Improve this question
Our sql server userid and password is known to a third party who is using our data integrated with his application bypassing us. He also uses the windows authentication to login and gets all the data required from the client side. I need to hide a few columns from others in sql server. I am aware of the data encryption which is not feasible at this stage and there are too many reports to be modified.
Is there a way to open a database connection along with a symetric/asymetric key and then use the same regular sql statements to read the data?
How to block sql server from logging in using Windows authentication?
Try this: Instead of allowin access to a full table, create a view with only the "public" columns, and give thrid party only access to that view. That way they cannot see you sensitive data columns. Blocking SQL to access from windows autentication is easy, only remove the user from the database.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 2 years ago.
Improve this question
I'm totally new in SQL Server. But I'm going to work on it from now.
I have been asked to research five methods to copy or access data from one remote SQL server(Location A) to another remote SQL server(Location B).
I found several method to achieve this goal, such as Linked Server, Openrowset
T-SQL function and SSIS(SQL Server Integration Service).
But are there API, VPN, SFTP, Cloud or another possibility to achieve this goal?
Your answer will be really helpful!
You dnt need to access any other method just make sure Location A Ip and port address is open in the firewall.
Also Location B Server should be accessible to location A
Access server You need below details:
ServerName with Port no
Database Id and Password.
Copy the data from A to B please see below:
you can generate the table script from server A run the same script on Table B.
If you want the Table with data from A then during the script
generation in last window where you need to select patch for script
file Just click on Advance option and then their select the Schema
type as Schema and Data then it will generate the Data script as well
for you.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 7 years ago.
Improve this question
I want to know when an application is pointing to a database, how to make sure that it is the correct database.
Can you let me know this from a Developer, DBA and a tester perspectives?
is it the database connection string? or update date on tables entries? any database scripts related check?
Thank you all in advance.
From a developer perspective, checking the connection string is the typical way to tell which database an application is pointing to. Of course, the big thing to look out for with this is making sure that you're looking at the right connection string, especially if you are using more than one of them in that application.
Depending on your application, you should be able to print a debugging message near your code that initializes the connection to the database that prints out the connection string that is being used for that connection. This could also allow the tester to know which database is being accessed.
From a DBA perspective, profiling the server could show active connections and/or queries with various amounts of detail depending on the database server being used.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I have written a project in C# which currently uses a SQLite database with 7 tables. Now I made a little mistake in selecting my database and since the application is going to be accessed by multiple users (~100) on a network the SQLite solution won't work because only one user can write at a time.
Now I want to switch to an Access (2010) database but my question is:
If I create the Access database with the same scheme as my SQLite database, do I have to change any of the SQL statements that I have written in my application? Or does this work interchangeable?
Also some side notes of why I am switching to an Access database instead of something like a SQL Server... Time does not allow this and costs neither.
Does anyone know what the impact will be if I'd simply replace the SQLite database with the Access database. And are there any differences in the SQL for these two for simple queries? I'm using things like 'INNER JOIN, IS NULL, SUM, COUNT'.
Thanks in advance!
are there any differences in the SQL for these two for simple queries?
For the simplest of queries, not really. For example, the specific language features you mentioned (INNER JOIN, IS NULL, SUM, COUNT) will likely work without modification, with the possible exception that Access SQL often requires parentheses when a statement contains multiple JOINs (example here).
Does anyone know what the impact will be if I'd simply replace the SQLite database with the Access database.
That is impossible to predict without a complete code review. You will really just have to try it and see what (if anything) breaks.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Slightly random one which has been bugging me for a while.
I am confused as to what actually makes a server a sever. I understand that a web-sever like Apache 'serves' web pages to the client. Why then is an SQL database server also called as such. What behaviours do the two entities have in common that make both of them servers? Or is it simply a case of same word - different meaning.
Appreciate any light shedding
Thanks
Dear Why we used "server" keyword in general scenario.
Server means, it serve the service.
So this keyword is associate because both are given service.
Sqlserver :- it store the actual data and give response as data to application response, comes from application which is hosted on application server. In sqlserver we can get/set the from various way like direct query of select/insert/update, via stored procedure, via application , used for SSIS, SSRS, SSAS services too.
Apache web server :- It is Web server, means a location where your application is actually hosted. It is used "WEB" keyword means it is used for web technologies and web application is hosted on that.
Both are different in terms of service, but give service or response as request comes, that why we called server.
An apache web server "serves" web pages to the client. An SQL database server "serves" databases to client applications. Applications need databases to store and extract data from, and a server provides them with exactly that.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm working on a large SQL Server database with no documentation. Is there a good, preferably free, documentation generator tool I can use to get my head around it.
One tool that I'm using more and more to do this sort of thing is LinqPad (www.linqpad.net). This is far more than just a Linq tool. It is very good at allowing you to drill down through table relationships, as long as FK's are properly in place. This tool is free.
On the non-free side, we also use Red-Gates SQL Doc (http://www.red-gate.com/products/sql-development/sql-doc/). Excellent tool.
You might want to have a look at my new (non-free, sorry) tool - LiveDoco - it's a web app that can be installed on an intranet IIS or even on a local IIS server and then you can just use your favorite browser to connect to a SQL Server database and see its structure/metadata, edit object descriptions or even search in DB object names (tables, columns, functions and their parameters etc.) and in the extended properties where the descriptions are usually stored (under “MS_Description”). And finally there is an export feature you can use to export all extended properties to a SQL file that you can run on a different DB of the same/similar structure to import/update your descriptions/notes there.
There is a fully functional (but read-only) online demo at http://www.livedoco.com.
This link will take you directly to the Person.Contact.ContactID column in the AdventureWorks sample DB from MS: http://demo.livedoco.com/livedoco/Explorer?Server=(local)%5Csql2k8xpress&Database=AdventureWorks#/?L0Name=Person&L1Name=Contact&L2Name=COLUMN_ContactID