How to Uninstall Microsoft Office?

All Windows users are familiar with this office suite developed by Microsoft and first released in 1989. It is made up of Microsoft office Excel, Word, OneNote, PowerPoint and Access. It is one of the most commonly used applications and it is used for both personal and business use.

Most of the times, the user removes such a useful program from the computer only when the program has become corrupted. Sometimes the user gets error messages when using one of the office applications, and then he definitely needs to remove the program.

The steps are fairly simple and novices in the field can avail the help of a step to step guide available in the Internet. Firstly, the user has to click on the 'Start menu' and click on 'Control panel'. In the Control panel, he needs to click on the option 'Programs and Features'. The screen will then display all the programs installed on the computer. From them, choose 'Microsoft Office' and then click on the option 'Uninstall'.

After this process is over you can be rest assured that you have successfully uninstalled Microsoft Office. The next step is to restart your computer for the purpose of cleaning up any registry settings, etc. There are chances that all the other associated files are not removed fully by this uninstalling procedure. There is an option to remove all the files manually but it is not a very practical option as there are bound to be many files and to search for them is a time consuming task.

There are advanced Uninstaller Programs which are completely free to download and will cleanly uninstall Microsoft Office and its associated files. There are a multitude of benefits in using these Uninstaller Programs. Firstly, it works better and more efficiently than the standard removal tool that comes with Windows. They help the user clean up all the registry entries that are corrupted or empty and help to improve the performance of the PC.

The most advanced feature of these Uninstaller programs is that they have an option called the 'Force Uninstall', which helps to fast detect the folder where the application is installed and it helps to forcibly remove the hidden applications installed in your system. The use of these Uninstaller programs also help to improve the performance of the PC as they clean up or delete the numerous applications that run simultaneously and cause delay in Windows start up times. As these Uninstaller programs are free, the user can get his work done efficiently without any purchase of costly programs.

Microsoft SQL Server 2000 Index Defragmentation Best Practices

Microsoft SQL Server 2000 Index Defragmentation Best Practices Author: Mike Ruthruff Microsoft Corporation February 2003 Summary: As Microsoft® SQL Server™ 2000 maintains indexes to … … reflect updates to their underlying tables, these indexes can become fragmented. Depending on workload characteristics, this fragmentation can adversely affect workload performance. This white paper provides information to help you determine whether you should defragment table indexes to benefit workload performance. To defragment indexes, …

Poorly Performing Queries When investigating any performance related problems, you must identify which queries in the workload are performing poorly. Some of the information discussed here is also used later in the paper to determine which indexes to focus on for defragmentation. You can use SQL Profiler to identify poorly performing queries. (For more information, see the topic “SQL Profiler” in SQL Server Books Online.) Running SQL Profiler introduces some overhead; however, monitoring only the following events should allow you to collect needed information with minimal impact on performance (this varies, but generally less than 10 percent impact to CPU utilization). SQL Profiler provides a trace template named SQLProfilerTSQL_Duration , which captures relevant events. You can use this to identify poorly performing queries quickly. You can also manually create a SQL Profiler trace that captures these events: • TSQL: SQLBatchCompleted • Stored Procedures: RPC:Completed The length of time you need to run SQL Profiler depends on the server workload. For the trace to be most useful, it should represent a typical workload or, at least, the part of the workload that exhibits poor performance. After the trace has been captured, examine the trace log focusing on the duration column. This is a measure in milliseconds of the duration of each batch or query. Identifying the Poorest Performing Queries Here are some suggestions to best determine the poorest performing queries in the trace: • Group the trace by query duration. Focus first on the “Top 10? worst performing queries. • If your application uses stored procedures extensively, consider using the SQLProfilerSP_Counts trace template to identify the most commonly called stored procedures. Focus on the worst performing stored procedures that are used most frequently. • Consider saving the collected data into SQL Server tables. This allows you to query the tables and perform more detailed analysis (for example, average duration, max duration, and so on) of the workload performance. Underlying Schema After you have identified the longest running/worst performing queries, you must ensure that the underlying schema is optimal for these. Ensure that appropriate indexes exist and are being used appropriately by the queries. Using SQL Query Analyzer to display and review query plans allows you to see what indexes are being used by queries in the workload. When the execution plan of a query is graphically …. Monitoring Fragmentation Levels Regularly monitoring fragmentation levels on indexes is good practice. For a sample script that demonstrates how to automate the capture and rebuild of heavily fragmented indexes, see the “DBCC SHOWCONTIG” topic in SQL Server Books Online. Consider using the DBCC SHOWCONTIG TABLERESULTS option and importing this information into tables at regular intervals. Doing this allows you to monitor the fragmentation levels over time. Also consider using the WITH FAST option when running DBCC SHOWCONTIG on a busy server. Using the WITH FAST option allows DBCC SHOWCONTIG to avoid scanning the leaf pages of an index. This can result in faster performance of DBCC SHOWCONTIG; however, because it does not scan the leaf pages of the index, it cannot report page density numbers. Table 1 shows the amount of time it took to run DBCC SHOWCONTIG against all the indexes in the small-scale and large-scale DSS environments. The ALL_INDEXES and TABLERESULTS options were used for each test. Table 1 DBCC SHOWCONTIG performance DBCC SHOWCONTIG options Total number of index pages (all indexes) Run time (minutes) Small-Scale Environment Not using the WITH FAST option 1,702,889 5.02 Using the WITH FAST option 1,702,889 0.90 Large-Scale Environment

Microsoft SQL Server Black Book

Brief Full Advanced Search Search Tips To access the contents, click the chapter and section titles. Microsoft SQL Server Black Book (Publisher: The Coriolis Group) Author(s): Patrick … … Dalton ISBN: 1576101495 Publication Date: 07/01/97 Search this book: Introduction What’s on the CD-ROM Dedication Chapter 1—Preinstallation Considerations What Is A Device? What, Then, Is A Database? What Are Character Sets And Sort Orders? What Is The Recommended System Configuration? Where Should The Microsoft SQL Server Be Installed? What …

up Microsoft SQL Server on a primary or backup domain controller. Keep shared file access off your database server. Having users copy files to and from the server will move the disk heads unnecessarily. Disk I/O is the slowest thing your data server will do. Do everything you can to keep it to a minimum. Also avoid sharing printers, modems, or like services on your Microsoft SQL Server. All of these processes are burst performance-related loads; Murphy’s Law will always ensure that one of the biggest file transfers or print jobs will hit your server at the same time a large query is running, causing the whole system to appear to hang. As you might be noticing, Microsoft appears to be moving toward a distributed server network. All the servers do not have to be on independent machines, but this configuration will help distribute the load across your network, allowing you to put lighter-weight and lower-cost servers in place for mail and file services and put your money where production is, such as on data services. This distribution can be a good thing, but many companies fail to recognize this until they have put all their eggs (applications, services, and files) in one or two baskets (servers). Plan for growth. By definition, databases will grow given even normal use. Over time any system that is being used in production will expand not only in feature and function, but in the amount of data as well. If possible, place Microsoft SQL Server on a machine by itself. Install it as a server that is part of a domain (provided you are using the Microsoft domain model). Place any other applications on separate machines when possible. If multiple applications are running on the same machine, you are complicating the process unnecessarily. In addition, beware of disk-intensive applications running on your database machine. If an application is writing to disk and Microsoft SQL Server is writing to disk, these processes will compete for disk I/O and slow down both applications…..

Microsoft SQL Server 2008 Database Engine Common Criteria Evaluation

Security Target SQL Server 2008 Team Author: Roger French Version: 1.2 Date: 2009-01-23 Abstract This document is the Security Target (ST) for the Common Criteria certification … database engine of Microsoft® SQL Server® 2008. Keywords CC, ST, Common Criteria, SQL, Security Target Security Target Microsoft SQL Server 2008 Database Engine Common Criteria Evaluation Page 2/56 This page intentionally left blank Security Target Microsoft SQL Server 2008 Database Engine Common Criteria ….

Security Target Microsoft SQL Server 2008 Database Engine Common Criteria Evaluation Page 9/56 Figure 1: TOE As seen in Figure 1 the TOE internally comprises the following logical units: The Communication part is the interface for programs accessing the TOE. It is the interface between the TOE and clients performing requests. All responses to user application requests return to the client through this part of the TOE. The Relational Engine is the core of the database engine and is responsible for all security relevant decisions. The relational engine establishes a user context, syntactically checks every Transact SQL (T-SQL) statement, compiles every statement, checks permissions to determine if the statement can be executed by the user associated with the request, optimizes the query request, builds and caches a query plan, and executes the statement. The Storage Engine is a resource provider. When the relational engine attempts to execute a T-SQL statement that accesses an object for the first time, it calls upon the storage engine to retrieve the object, put it into memory and return a pointer to the execution engine. To perform these tasks, the storage engine manages the physical resources for the TOE by using the Windows OS. The SQL-OS is a resource provider for all situations where the TOE uses functionality of the operating system. SQL-OS provides an abstraction layer over common OS functions and was designed to reduce the number of context switches within the TOE. SQL-OS especially contains functionality for Task Management and for Memory Management. For Task Management the TOE provides an OS-like environment for threads, including scheduling, and synchronization —all running in user mode, all (except for I/O) without calling the Windows Operating System….. Security Target Microsoft SQL Server 2008 Database Engine Common Criteria Evaluation Page 11/56 Table 1: Hardware and Software Requirements CPU ? Pentium III compatible at 1 GHz or faster (for the 32 bit edition) ? AMD Opteron, AMD Athlon 64, Intel Xeon with Intel EM64T support, Intel Pentium IV with EM64T support at 1.4 GHz or faster 1 RAM 512 MB Hard Disk Approx 1500 MB of free space Other DVD ROM drive, display at Super VGA resolution, Microsoft mouse compatible pointing device, keyboard Software Windows Server 2008 Enterprise Edition (in 64 or 32 bit) , English version, version 6.0.6001 .NET Framework 3.5 SP 1 Windows Installer 4.5 The following guidance documents and supportive information belong to the TOE: ? SQL Server 2008 Books Online: This is the general guidance documentation for the complete SQL Server 2008 platform ? SQL Server Guidance Addendum / Installation / Startup: This document contains the aspects of the guidance that are specific to the evaluated configuration of SQL Server 2008 The website https://www.microsoft.com/sql/commoncriteria/2008/EAL1/default.mspx contains additional information about the TOE and its evaluated configuration. Also the guidance addendum that describes the specific aspects of the certified version can be obtained via this website. The guidance addendum extends the general guidance of SQL Server 2008 that ships along with the product in form of Books Online. This website shall be visited before using the TOE. 1.3.3 Architecture of the TOE The TOE which is described in this ST comprises one instance of the SQL Server 2008 database engine but has the possibility to serve several clients simultaneously. 1.3.4 Logical Scope and Boundary of the TOE SQL Server 2008 is able to run multiple instances of the database engine on one machine. After installation one default instance exists. However the administrator is able to add more instances of SQL Server 2008 to the same machine. The TOE comprises one instance of SQL Server 2008. Within this ST it is referenced either as “the TOE” or as “instance”. The machine the instances are running on is referenced as “server” or “DBMS-server”.

Microsoft SQL Server 2000 Security

The SANS Institute Page 1 of 6 Microsoft SQL Server 2000 Security The following is a checklist of security guidelines to follow in securing Microsoft SQL Server 2000. It is divided into categories: 1) Setup and General Issues, 2) Authentication, Users and Logins, 3) Permissions, 4) Logging, and 5) Applications. Within each category, the guidelines are described as Mandatory, Recommended or Paranoid; these labels are intended to help you prioritize your actions and to weigh the relative importance of each …

Setup and General Issues • [Mandatory] The Internet firewall should block all packets going to or coming from the database servers. Consider regulating traffic from the internal LAN as well. SQL Server primarily uses TCP 1433 for data sessions and UDP 1434 for pre-session handshaking. But be aware that SQL Server can also use UDP 137, TCP 139 and TCP 135. • [Mandatory] Stay abreast of the latest Service Packs and hotfixes, and install them as soon as feasible; however, do not blindly install Service Packs or hotfixes without first testing them on non-production servers, and without first backing up the production server. Keep in mind that SQL Server has Service Packs separate from the operating system’s Service Packs. • [Mandatory] Physically secure database servers and their backup media in locked, access-controlled rooms. Provide electronic surveillance when appropriate. • [Mandatory] In general, disable services or features of SQL Server that you are not currently using, such as SQL Mail. • [Mandatory] Scan the database server with the Microsoft Baseline Security Analyzer (MBSA) or similar auditing tool to reveal common insecurities. • [Mandatory] Regularly audit all shared folders on the database server to ensure that all permissions are minimal and that none of the shares are unnecessary. Be especially wary of shared folders that permit Write access. • [Mandatory] When replicating databases over the Internet, set up a router-to- router Virtual Private Networking (VPN) tunnel to connect the two LANs. When replicating over untrusted internal networks, use IPSec to encrypt the replication traffic. • [Mandatory] Assign a long and complex password to the SQL Server service account (preferably 25 characters or more, with 15 characters the minimum)….. • [Mandatory] The setup program for SQL Server should have done this already, but set the NTFS permissions on all database-related files, including the SQL Server binaries, to permit only Read & Execute to Authenticated Users, and Full Control for System, Administrators and the SQL Server service account. If you change the SQL Server service account, do it using Enterprise Manager so that permissions will be changed automatically. • [Mandatory] Use NTFS audit settings (SACLs) to track failed access to database-related files. • [Mandatory] The setup program for SQL Server should have done this already, but, on the following registry keys, remove all permissions for the Everyone group and grant Full Control to the SQL Server service account and local Administrators, then audit all failed access and all successful writes to them as well: HKLM\Software\Microsoft\MSSQLServer (for a default instance) or HKLM\Software\Microsoft\Microsoft SQL Server\ Instancename (for a named instance, if any). • [Mandatory] Delegate authority over the server and its databases by utilizing fixed server and database roles appropriately, or by creating your own custom roles, so that excessive power is not being placed in the hands of those who don’t need it. In short, do not simply place everyone in the sysadmin role out of convenience. • [Mandatory] All database and server management scripts should be stored in an access-controlled NTFS folder. Audit all access. Scripts should not contain hard- coded passwords. Consider digitally signing these scripts using the Windows Script Host (WSH) 5.6 or later, and warn on the attempted execution of scripts that fail signature verification. • [Recommended] Disable cross-database ownership chaining (KB810474). It is disabled by default after SP3 is applied to SQL Server 2000. • [Recommended] Regularly audit what the Public role has access to. This role is roughly equivalent to the Everyone group in the operating system. Remove or limit the rights of the Public role whenever possible, but do not explicitly deny permissions for it (simply remove them). • [Recommended] Regularly audit who has Execute permission on all stored procedures, especially xp_cmdshell. The Guest and Public logins rarely need the Execute permission. When in doubt, grant permission only to the sysadmin role. • [Recommended] When using UDL files, assign restrictive NTFS permissions and audit all access to the files. Avoid storing passwords in UDL files by using Integrated Windows authentication.

Configuring ViewPoint with Microsoft SQL Server 2000

VIEWPOINT Configuring ViewPoint with Microsoft SQL Server 2000 Introduction Many customers inquire whether Viewpoint will work with Microsoft SQL Server 2000 (MS SQL Server). Viewpoint can be configured to run with MS SQL Server, but SonicWALL does not provide any technical support for this configuration . Due to the number of inquiries, this document is provided only as a courtesy to our advanced SQL Server savvy customers that want to use this configuration. This document presents a procedure to remove the MSDE …

9) Edit \Tomcat\webapps\sgms\WEB-INF\web.xml and modify the following lines:
dbhost 127.0.0.1\SNWL dburl jdbc:inetdae7a:127.0.0.1/SNWL dbuser BAB7E1B 9875 CF081 dbpassword EE80851182B4B962FC3E0EDF1 F00275A to
dbhost 127.0.0.1\SNWL dburl jdbc:inetdae7a:127.0.0.1/SNWL dbuser BAB7E1B 9875 CF081 dbpassword EE80851182B4B962FC3E0EDF1 F00275A to dbhost 127.0.0.1 dburljdbc:inetdae7a: localhost: 1433 …. dbhost 127.0.0.1 dburl jdbc:inetdae7a: localhost: 1433 dbuser Us ern a me dbpassword Password Note : Replace localhost and 127.0.0.1 if the SQL Server 2000 database is running on a remote machine and not on the ViewPoint server. Note : Replace Username and Password with the encrypted strings generated earlier with the java command in step 5. 10) Backup the existing \SQL\bldMSDB.bat. 11) Go to the SQL Server 2000 Database. Before installing SonicWALL Viewpoint using Microsoft SQL Server 2000, complete the following procedure: a. Install Microsoft SQL Server 2000 on a server. b. When prompted, select “Create a new instance of SQL Server, or install Client Tools” option. c. When prompted, select the “Server and Client Tools” option. d. When prompted, select the “Typical” setup type. e. When prompted for an authentication mode during SQL Server 2000 installation, make sure to select Mixed Mode . Do not select Windows Authentication Mode . After successfully installing SQL server 2000, Service Pack 4 or later needs to be applied. f. Once the database is installed, click Start , point to Programs , point to Microsoft SQL Server , and click Enterprise Manager . g. Expand the Security tree. Right-click Lo gins and select New Login . h. Create a SonicWALL Viewpoint database user (The non-encrypted text of the username you decided on in step 5 with the java command). For this database user, select the SQL Server Authentication mode option and enter the non-encrypted password for this user. Make sure to assign this user the Database Creator server role. i. Exit from the SQL Server Enterprise Manager.

How Microsoft wins against GNU/Linux in schools

microsoft, posted: 14-Jan-2009 07:09

Very interesting discussion on Slashdot here. The articles that are linked to and the discussion itself provide insights into the various strategies that Microsoft uses to ensure its presence in educational institutions and to prevent Linux from being used in schools instead. The biggest fear is to 'lose against Linux' and to give up on the for-free Microsoft training that tax-funded, public schools are unwittingly providing for Microsoft.

The discussion also mentions Microsoft's "Unl(read the entire post)...

Permalink to