you cant take cold backup without interupting the mirror because when you go for cold backup then you have to shutdown all sql server services

you can take hot backup as...

Total Processors ?

Total RAM ?

Total Drives ?

OS version ?

As Gila Said provide complete information

Execute these queries when user complain regarding performance or if you feel and then provide result of these queries

For Memory Presure

==================

select * from sys.dm_os_performance_counters

where...

Provide Execution PLan

and check IOs of particular Query ,execute these queries in the morning and send the result

For Memory Presure

==================

select * from sys.dm_os_performance_counters

where counter_name like 'page life%'

For Queries Utilizations

========================

SELECT...

is there any other load of DML on these tables ?

Provide Execution Plan ?

Check Statistics of these tables are updated ?

Check Fragementation of Indexes of these tables ?

Create Cluster index...

you cant create objects on a particular File,you can create objects in a different File groups and then File groups have multiple files

CREATE TABLE [dbo].[TEST]([Id] [int] NOT NULL) ON [PRIMARY]...

yes you can

First create the same table as DMV and then insert data after required interval at the end of day you can check CPU and memory usage for certain...

After these flags you can see full memory in your OS level ?

If yes then enable the AWE and lock pages for the SQL Server Service Account and then restart...

Create the ODBC connection and then create linked Server with Microsoft OLE DB for ODBC drivers

Use Row Versioning if you are facing lots of lock in your database

Both are different ,in the case of with(nolock) ,owner and other users will see the uncommitted data but...

no you can't because accordoing to the microsoft Active\Active means multple instances on multiple nodes

there is no load balancing for a instance like a RAC in oracle

For High Availability you should use

1-Cluster

2-Mirroring

3-Log Shipping

4-Replication

For point in time recovery you should use

1-Full Recovery Model

Databse Model,its depends on the policy of your organization ,how much data loss they can...

SQLName same machine exist on the network ?

can you ping IP address of this SQLName ?

can you ping any DNS name in the network ?

1-Take Full Backup in the shared folder of network 1 and then other network have rights to restore from this shared folder

2-You can Use FTP from 1 network to another...

dbo is for default,revoke the permission from the dbo schema on the other users,whenever users create any objects then they will restrict to create their own objects in their schema...