Transaction in middle of SQL Server Full bckup [closed] - sql-server

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.

Related

Can differential backups interfere with the SSIS job process? [closed]

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 2 years ago.
Improve this question
I want to ask about the differential backup that happens in SQL Server 2012.
What I want to ask are when the job is started, will the backup plan will stop all SSIS job?
What I want to ask are when the job is started, will the backup plan will stop all SSIS job?
There is no actual need to stop SSIS jobs during the backup.
However, it still can be planned to run in own maintenance time window, which not interferes with user jobs due to reason stated below.
Backup task is fully online operation. It will not cause any locks or downtimes.
However, it can impact performance of your SSIS package because it can hit IO and network subsystems of the server.

Should we have a SQL maintenance plan for TFS Server 2015/2017? [closed]

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.

Database Health - SQL Server [closed]

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.

How to undo TRUNCATE command [closed]

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 accidently executed TRUNCATE command on a wrong table and all my data is gone. We do have a backup but its 2 weeks old and doesn’t have all the latest data.
Any ideas how can we rollback this command and get the data back if possible? Are there any third party tools that can do this?
Simple answer is – you can’t rollback a transaction if it’s already committed but you can do something else to get the data back (or at least some parts of it).
When you execute truncate statement your data is still in the MDF file but it’s not visible because SQL Server is now treating this as free space (truncate is basically telling SQL Server to deallocate data pages).
Only way to get the data back is to somehow read deallocated data pages and convert them into readable data.
Important: you must act fast because free space will be overwritten with new data if not already. If you can stop your SQL Server instance and make a copy of MDF and LDF files that would buy you more time.
Try using ApexSQL Recover. From what I know it’s the only available tool that can do this kind of restore. If you’re really good with SQL you can try modifying and executing very long script like this .
Unless it was Transaction Wrapped, I am afraid you are out of luck.
Here is a similar post, but this also has more explanations.
http://www.sql-server-performance.com/forum/threads/how-to-rollback-truncate-operation.16968/

Monitoring SQLServer [closed]

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'm seeking for a solution to monitor (with graphs) the status of my MSSQL instances during a periode of time (day or night) and get or make reports for that monitoring.
Does any one have or know any known simple solutions to do so please ?
Thank you for your help.
Depends on what you want to monitor. There are vendor products that will do it. Idera has Diagnostic Manager and RedGate has SQL Monitor to name just a few. Or if you don't want to spend any money SQL Server has several monitoring options including alerts, policy based management and data collection. These won't be as pretty and may not cover as much not to mention you will be writing some code on your own, but they are free (with SQL Server of course, depending on edition).
Related, though you'll want to edit the scripts for getting information is Ola Hallengren's maintenance solutions http://ola.hallengren.com/. There are useful scripts for maintenance, but depending on what information you're trying to obtain, you can build on these scripts to get information. From there, you can use the results of these queries in SSRS to populate graphs, or even use a tool like Excel.
Again, Ola Hallengren provides maintenance solutions, so these will need to be adjusted for monitoring (depending on what you're monitoring), but they are totally free and you can edit the scripts, as well as see where the information comes from so that you can determine what you need to monitor.

Resources