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
My database has 16MB of space left
I used to just truncate as I was taught but I found these links that advise against truncating
http://www.sqlskills.com/blogs/paul/why-you-should-not-shrink-your-data-files/
http://blog.sqlauthority.com/2011/01/19/sql-server-shrinking-database-is-bad-increases-fragmentation-reduces-performance/
Is there anything else I can do on my database to reduce the size other then deleting table records? Any advise would be greatly appreciated.
You should most definitely look for ways to increase storage space as a long term solution. Having only 15MB left in database can easily lead to corruption and database going offline.
If you’re on SQL Server 2008+ you can try to enable its native data compression.
Related
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 4 days ago.
Improve this question
I am having an issue with my SQL Server transaction log filling up with the error:
The transaction log for database 'X' is full due to 'ACTIVE TRANSACTION'
I am having difficulty trying to find out what the effect on the transaction log is, when running a JDBC batch instead of a many smaller SQL executions.
SQL-Server is version 2012.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 5 years ago.
Improve this question
We installed TFS Server 2015 Update 2 in September 2016 and we are wondering if we should have a SQL maintenance plan (to rebuild indexes for example) on TFS.
In the documentation, they explained how to set it up, how to setup the backups, but nothing about the maintenance plan.
Is there anyone that tried it out? Is it worth it?
Thanks!
You shouldn't. TFS has its own "Optimize Database" jobs for index maintenance.
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 7 years ago.
Improve this question
If someone asks me to check the database health in a particular SQL Server database, which has been running for couple of years, what are the possible areas that I need to check? Do we have any tools to support for that?
Kindly provide some recommended links also to refer.
You need to do two things (at a bare minimum):
Make sure that backups are being taken on a regular basis and that at least once a full restore was done from the backups and that the restore was verified to contain valid, up to date, data.
https://msdn.microsoft.com/en-us/library/ms187510.aspx
Run 'DBCC checkdb' on the instance. It will take a while and can be a resource hog (you may want to run it at night or over a weekend.) Be very careful in reading the results and figuring out what to do if it detects errors.
https://msdn.microsoft.com/en-us/library/ms176064.aspx
http://www.sqlskills.com/blogs/paul/category/checkdb-from-every-angle/
If you do the above you may be held responsible for any, and all, issues that will ever occur to SQL Server including data entry errors.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
If the full backup is started at 11 and completed at 4. at 2.30 there are some transaction happened. Will it be reflected on this full back up file?
Check out these links from Paul Randal.
http://www.sqlskills.com/blogs/paul/a-sql-server-dba-myth-a-day-3030-backup-myths/
http://www.sqlskills.com/blogs/paul/debunking-a-couple-of-myths-around-full-database-backups/
http://www.sqlskills.com/blogs/paul/more-on-how-much-transaction-log-a-full-backup-includes/
Like many things in the database area, it all depends.
The last article is the best since it has the picture. If the database read operation completed after the transaction, then part of the log will be in the backup.
The best way to recover to 2:30 is to do a point in time restore.
Restore the backup, any log files, and use the STOP AT command to get to the exact time you want.
http://technet.microsoft.com/en-us/library/ms179451.aspx
Transactions are related to transaction log.
So after full backup , get a transaction log backup in order to be able restore database at a certain time.
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 have web application that will be similar to forums. I plan to have few thousands+ users on this application, and i wonder if i can use MS SQL Express - here is the list of it's limitations:
Despite the cpu usage, i wonder if this 1 GB of memory usage is enough. Can anyone tell me if this might be enough, or maybe give me some examples when this 1 GB would be enough.
I think it should be fine. Depending on how many columns you have in each row and their types, you should be able to get at least 1 million rows into 1GB of disk space. The database will only load as much of that table as it needs in memory. If it reaches its memory limit it will start paging.
If you are using SQL 2008 R2, then the actual database can only grow up to 10GB which is the real limit you should be concerned about.
In our database, our tables that are around 1GB contain about 4 million rows. We have 2 databases that are 50GB and the one takes up 16GB of RAM and the other 2GB. So it depends on how often and which tables are accessed.