SQL: Move TempDB to dedicated drive

Hi,

Best practice is to use a dedicated fast disks for your tempDB.
The TempDB DB gets used by all the Databases as far as i can understand so there can be quite a load on it.

A 15Gb drive should be enough.
It is much easier to change the TempDB file location at installation but this is a step lots of people don't do.
Would even be better if you can split the TempDB's LDF and MDF files over different drives but this all depends on your budget.

When i talk different drives i talk about different spindle power...Different VHD's on the same hard drive defeats the purpose of this exercise

Script:
USE master
GOALTER DATABASE TempDB MODIFY FILE(NAME = tempdev, FILENAME = 'G:tempdb.mdf')GOALTER DATABASE TempDB MODIFY FILE(NAME = templog, FILENAME = 'E:templog.ldf')GO

After this restart SQL and you are all-done

An operation failed because the following certificate has validation errors. The root of the certificate chain is not a trusted root authority..

Hi,
Just had a stressful few hours but error is now resolved...
Had this error:

An operation failed because the following certificate has validation errors:\n\nSubject Name: The root of the certificate chain is not a trusted root authority..

Basically anywhere where you try and open a infopath form you got an data source error saying access was denied and you must look on the Application log.

The application log was full of the errors above. Also in the ULS Logs.

Everywhere i searched pointed me to Trusted Root Authorities and "Manage Trust" under SharePoint Central Admin...Nothing worked...

Then this error popped up once:

Insufficient SQL database permissions for user 'Name: domain\Username SID: S ImpersonationLevel: None' in database '' on SQL Server instance. Additional error information from SQL Server is included below.

The EXECUTE permission was denied on the object, database, schema 'dbo'.

The user in the error was the SharePoint installer account which was suspicious. The error are in the logs for other users.

We compared the security rights in SQL for the user to QA and it only had Public access rights.

Added SecurityAdmin and DBCreator and after a IISReset is was working again.

Got no idea how the rights might have changed but at least it is solved now.

Hope this helps you.

Change the order of your Office Infomation Panel

Hi,

i Like to have the mandatory fields of my Information Panel first. Here is according to me the easiest way to change the order.

Open you Library and go Library Settings:

Then Click on Document Information Panel settings and "Create a new custom Template"
This will open InfoPath and after you click finish on InfoPath it will open your Panel...
Move around and do what you want to do and then save(to local machine) it and publish it.

and click publish on the next window and then close.