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 9 years ago.
Improve this question
I've a question that I can't seem to find an answer to (and I can't test it out for a few weeks so I'm doing research now during my downtime).
Should I be creating corresponding LOG files for every DATA file I create?
eg. if I create tempdev3.mdf, should I also create templog3.ldf?
Or do the LOG files get created automatically as and when needed by the SQL Server?
I'm using MS SQL 2008 R2 EE but I think the answer equally applies to 2005 and 2012.
You can have multiple log files, but there is no point, SQL Server will only write to them one at a time sequentially, so there is no performance gain here at all.
All you do with having multiple log files is create more files to manage and potentially more downtime after a crash as there is possibly more log file than strictly necessary to initialise.
Have a quick look at the following article for a bit more info:
Multiple log files and why they’re bad
Bottom line, don't bother with it.
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 new to the topic of databases and DBMS.
I have written the PhoneBook program with C# .NET and SQL Server.
My question is how can I run this program on a users computer who hasn't got SQL Server?
I want when they click on the execution file on their computer, it will work immediately and correctly and they can store new users or delete some user
You could host a SQL server for your users and require they have an internet connection.
You could rewrite it as a web application, also requiring an internet connection.
Or you can use SQLite, an embedded SQL client and, for lack of a better term, server. That's what I'd recommend, and that's what many applications do. SQLite is not fully compatible with SQL Server, so you'd have to rewrite some of your SQL.
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 8 years ago.
Improve this question
I am new to sql server, Which method is best to work with sql server COMMAND LINE OR GUI.
What do you mean "work with"?
I would say that that Microsoft SQL Management Studio, should be more than sufficient for anything you want to do. Using this should almost make any task relatively simpler than using CLI.
For regular usage, I use the GUI interface. It has access to everything I need to do within one or two clicks. For automation tasks, or to interact with the service when the GUI is hanging, I use the command line.
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.
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 10 years ago.
Improve this question
I am trying to backup my SQL Server 2008 R2 database. However I am getting the below error, no matter where I try to save the backup.
System.Data.SqlClient.SqlError: The volume on device 'D:\Programfiles\Microsoft SQL Server\MSSQL.1\MSSQL\Backup\dbName.bak'
is not part of a multiple family media set. BACKUP WITH FORMAT can be
used to form a new media set. (Microsoft.SqlServer.Smo).
Can anyone throw light on this?
The only helpful links I could google were following but of little use:
http://social.msdn.microsoft.com/Forums/en-US/sqldisasterrecovery/thread/a1eb2818-2a97-4c52-aa8d-7c224f1ac282
and
http://www.sqlservercentral.com/Forums/Topic279584-24-1.aspx
I wasn't able to reproduce the issue however, here's a workaround for whoever might run into this: use WITH FORMAT clause or Options - Back up to a new media set and erase all existing backup sets option in the GUI.