appunti semiseri di un presunto tecnico

When the transaztion log is full, you can truncate it by using this query:   USE DatabaseName GO DBCC SHRINKFILE(<TransactionLogName>, 1) BACKUP LOG <DatabaseName> WITH TRUNCATE_ONLY DBCC SHRINKFILE(<TransactionLogName>, 1) GO   <TransactionLogName> is the name of the t log without extension and path   _____________________________________ Stefano Mazgon  

Fix : Error Msg 1813, Level 16, State 2, Line 1 Could not open new database ‘yourdatabasename’. CREATE DATABASE is aborted. This errors happens when corrupt database log are attempted to attach to new server. Solution of this error is little long and it involves restart of the server. I recommend following all the steps below in order without skipping any of them. Fix/Solution/Workaround: SQL Server logs are corrupted and they need to be rebuilt to make the database operational. Follow all the steps in order. Replace the yourdatabasename name with real name of your database. 1. Create a new database with same name which you are trying to recover or restore. (In our error message it is yourdatabasename ). Make sure the name of the MDF file (primary data file) and LDF files (Log files) same as previous database data and log file. 2. Stop SQL Server. Move original MDF file from older server (or location) to new server (or location) by replacing just created MDF file. Del...

The root cause of the dual monitor problem is a task in the task scheduler called TMM (Microsoft Transient Multi-Monitor Manager). I disabled this task, and all seems to work fine now.   _____________________________________ Stefano Mazgon  

Dovuto al bluetooth, tra i plugin rimuovere il btsendto_office.dll. Il service pack 2 non risolve. _____________________________________ Stefano Mazgon

http://www.piriform.com/ CCleaner Optimization and Cleaning Defraggler File Defragmentation Recuva File Recovery _____________________________________ Stefano Mazgon  

  If your chkdsk runs on every boot, here are some things you can try. First of all, let it run once completely. Then try this : Run regedit Edit: HKEY_LOCAL_MACHINE\SYSTEM\ CurrentControlSet\ Control\ Session Manager Change the BootExecute entry from: autocheck autochk * /. To: autocheck autochk * Or else try this : Start> Run> bring up a command prompt by typing in “CMD” and type ” fsutil dirty query g: “. This queries the drive, and more than likely it will tell you that it is dirty. Next, type “CHKNTFS /X G:”. The X tells Windows to NOT check that particular drive (G) on the next reboot. At this time, manually reboot your computer, it should not do a Chkdsk and take you directly to Windows.   Once Windows has fully loaded, bring up another CMD prompt and type and now you want to do a Chkdsk manually by typing “Chkdsk /f /r g:”. This should take you through 5 stages of the scan and will unset that dirty bit. Finally, type “fsutil dirty qu...

http://support.microsoft.com/kb/258034 _____________________________________ Stefano Mazgon