Viewing 15 posts - 1,021 through 1,035 (of 1,319 total)
GilaMonster (7/15/2008)
-- You can't be late until you show up.
July 18, 2008 at 11:05 am
One other thing you can do, prior to shrinking the log file, is "backup log 'databasename' with truncate_only". This will cleanse the log, as much as possible. Then issue the...
-- You can't be late until you show up.
July 17, 2008 at 12:28 pm
Shrinking the log file is not so bad, if necessary. Shrinking the data
file(s) is truly not recommended. It will lead NTFS fragmentation and will definitely fragment your indexes, leading...
-- You can't be late until you show up.
July 17, 2008 at 12:13 pm
Simply backing up the log does NOT reduce the size but it frees up the unneeded transactions from the log, creating space within the log for additional, new transactions. You...
-- You can't be late until you show up.
July 17, 2008 at 9:00 am
Can you create an index on formid? That should help. Also, can you narrow down the information being returned? "Select *" will have a negative performance impact as well and...
-- You can't be late until you show up.
July 17, 2008 at 8:15 am
amjadpathan, while I'm sure your intentions are good, you do know you've responded to a thread that's been dormant for 30 months, don't you?
-- You can't be late until you show up.
July 17, 2008 at 8:01 am
rinu philip (7/17/2008)
When SQL Server is installed the setup program creates tempdb database. Tempdb is a system database used by SQL Server to store temporary tables and...
-- You can't be late until you show up.
July 17, 2008 at 6:12 am
usman.tanveer (7/16/2008)
Right Click on your database-->Tasks-->Shrink-->FilesSelect 'Log' from file type drop down. Press ok.
Backup your log files before you shrink them otherwise your simply wasting your time.
-- You can't be late until you show up.
July 16, 2008 at 8:07 am
I assume your databases as set to full or bulk-insert mode so issue a backup log dbname command from QA (check BOL for exact syntax) or setup a maintenance plan...
-- You can't be late until you show up.
July 16, 2008 at 8:03 am
The true issue is network connectivity and somehow I don't think a hotfix is going to cure that. One blip in the connection/Nic and the backup is worthless. Can you...
-- You can't be late until you show up.
July 16, 2008 at 6:20 am
GilaMonster (7/14/2008)
TempDB is completely recreated every time SQL starts. What you're seeing is normal and expected.
Gail already answered that question. Your user databases do not get recreated on restart so...
-- You can't be late until you show up.
July 15, 2008 at 6:44 am
In additon to all your database backups, I'd backup all binaries as well. You never know, this could get you back to your current state in the event of upgrade...
-- You can't be late until you show up.
July 15, 2008 at 6:36 am
Ben Blum (7/13/2008)
it was obvious the physical dick had become corrupt.
Sounds PAINFUL! - Sorry, a little (very little) Monday morning humor to kick off the week....:Whistling:
-- You can't be late until you show up.
July 14, 2008 at 7:33 am
This cleans up your script. Not sure if it'll produce what you're looking for. Can you provide the views, tables, sample data and expected output? And look at the bold...
-- You can't be late until you show up.
July 11, 2008 at 9:51 am
I believe these would add credence to why backing up over the network is not recommended. It's definitely network connectivity or loss there of.
Can you backup local and then copy...
-- You can't be late until you show up.
July 11, 2008 at 9:45 am
Viewing 15 posts - 1,021 through 1,035 (of 1,319 total)