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 9 years ago.
Improve this question
If any site has hacked means how much percent has said that the back end of that site database will be safe.
How to prevent the SQL Tables from hackers and what are the suggestions for this type of issues?
How to prevent the SQL Tables from hackers?
There are entire books written on this subject. The first thing is to make sure that the user access to SQL Azure from their web software can only select, insert, and update.
Have different administrative software with a different user access for table create, table update, and row delete.
How to enter those thousands of data manually?
Get a bunch of computers and hire temporary workers to key the data.
A journey of ten thousand database rows begins with a single entry.
Related
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 2 years ago.
Improve this question
I'm hoping for some opinions on the best options for how to replicate, in real time, data from a production SQL Server database onto another SQL instance. This second instance would be for vendors who need to access some of the tables from the production database, but we would prefer that they not directly access our production instance.
I have some awareness of transactional replication and log shipping as possible solutions, but I would be interested in pros/cons of these approaches, or superior alternative solutions you may have tried.
I realize there are many topics already on Stack Overflow that discuss how to do this, but many that I found were older (technology's always changing), or focused on a very specific scenario.
For read-only access you can use AlwaysOn Availability Group feature introduced with SQL Server 2012
Documentation:
https://learn.microsoft.com/en-gb/sql/database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server?view=sql-server-ver15
https://learn.microsoft.com/en-gb/sql/database-engine/availability-groups/windows/configure-replication-for-always-on-availability-groups-sql-server?view=sql-server-ver15
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
i'm so confuse now to design good architecture for financial transactional system.
For example :
i have some tables :
MSMembers (for provide member profile and username password of member)
TRTransactions (table record all transaction that comes from other host, such as member's host)
MSFees (list for tiering fee related with number of the transaction)
In my opinion, i think i can :
Separated the database for transactional and master data. For example,
DBMaster : MSMembers, MSFees;
DBTransaction : TRTransactions
So my application (my TransactionService not the web), must connect to multiple database, is it effective if my service connect to multiple database?
Or, same with point 1, but i create MSMembers and MSFees in the DBTransaction, so TransacionService doesn't need connect to multiple database.
Please some advise for this case.
Thanks before. :)
There is no reason to go with separate databases unless you are on MySQL (and in which case database means schema in other databases). Additionally it isn't clear why you would separate these into different schemas in the first place. There is really nothing to gain from this unless you want effectively to use different schemata to manage different sides of your application.
So keep everything in one database. Much easier that way, and you can enforce real database constraints (referential integrity etc) between the parts.
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
My setup is as such. I have an MS Access front end which points to a linked table in SQL Server. Via the form, the user updates one of the fields in the linked table throughout the day. My query is how do I update another column with today's date whenever a user changes it manually in the MS Access front end?
Thanks in advance for your time and help.
There is a nice discusion of this problem here: Best way to implement a last-modified column in Sql Server 2005?
The accepted answer that time around was to use a TRIGGER.
There are lots of good reasons to avoid triggers (see http://devproconnections.com/sql-server/reasons-avoid-triggers). But auditing can be hard to achieve by other methods.
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 got a requirement from client to create a new database when somebody insert new record in a specific table. I want to have all the tables, stored procedure and other things in the new database from the current database.
I am planning to restore the current database with the new Name.
Can anybody tell me how to do this.
Although this seems a pretty strange thing to do, if you really have to then create an Agent job that simply restores the database from a backup. In the trigger, you could run the job with:
EXEC msdb..sp_start_job #job_name = 'JobName'
I imagine you also need to pass some parameters to that job. You can store those in a table in a database (preferably a central one).
Anyway, I'd be more in favor of creating the database from scripts (schema and data), since it's easier to maintain.