Viewing 15 posts - 1,141 through 1,155 (of 1,319 total)
To reiterate various comments already made in this thread: If the database is sent to simple recovery mode, no you cannot backup transaction logs. With respect to Onepoint (if that's...
-- You can't be late until you show up.
May 16, 2008 at 2:34 pm
Are you trying to delete all records on a table? If so, truncate table has low overhead with respect to logging. You can delete in small rowsets and backup the...
-- You can't be late until you show up.
May 16, 2008 at 2:19 pm
Did you check out this thread (same forum, a little bit older)? I don't use rtf within SQL but seems to be some useful items.
http://www.sqlservercentral.com/Forums/Topic220973-23-1.aspx
-- You can't be late until you show up.
May 16, 2008 at 9:23 am
Maybe I misunderstood something here. I thought you were profiling your user community as when you run these same queries in QA, there are no issues. What exactly are you...
-- You can't be late until you show up.
May 16, 2008 at 9:16 am
What kind of connection do they have to the database server? Bandwidth can be a killer, especially depending on the size of the resultset being returned.
-- You can't be late until you show up.
May 16, 2008 at 9:01 am
Just my 2 cents but as Ola stated, you now would have a single point of failure and need to scramble to restart/create backup jobs elsewhere, whether another single machine...
-- You can't be late until you show up.
May 16, 2008 at 8:48 am
Quality and consistency for me today!. I recently started a new job. My old company, everything was new and was built quickly but consistently (not always quality) so anyone could...
-- You can't be late until you show up.
May 16, 2008 at 7:18 am
It appears the reboot did the trick. Strange indeed. I should have stated in my original post that this is running on VMWare and ESX server, which was installed in...
-- You can't be late until you show up.
May 15, 2008 at 12:04 pm
Good point, didn't even think about that option. And it saves disk space!
-- You can't be late until you show up.
May 15, 2008 at 11:34 am
Why not take your full backup after your index rebuild and log backup? Then, if you do need to recover, simply restore the full (and potentially other, smaller t-logs) and...
-- You can't be late until you show up.
May 15, 2008 at 11:23 am
Brain cramp!:blush: Right click on the job and generate SQL scripts.
-- You can't be late until you show up.
May 15, 2008 at 7:36 am
What exactly are you trying to accomplish? The maintenance jobs grow the t-log as needed. Are you simply trying to save disk space? I'd continue doing things the way you...
-- You can't be late until you show up.
May 14, 2008 at 1:03 pm
Steve Jones - Editor (5/9/2008)
Good advice above from Tom.I think backups and security are most important, but it's good to get the other information listed above.
Steve, it's Terry, not Tom....
-- You can't be late until you show up.
May 9, 2008 at 9:24 am
Darryl, be aware that if you restricted your log to 2GB and the log needs to grow beyond that, all processing will stop until someone manually increases the size or...
-- You can't be late until you show up.
May 9, 2008 at 7:43 am
I've never seen the SQL Server Agent stop because it has no work to do. Most of my scheduled jobs run overnight and the agent never shuts down. Check the...
-- You can't be late until you show up.
May 9, 2008 at 7:38 am
Viewing 15 posts - 1,141 through 1,155 (of 1,319 total)