Truely, you should not allocate all your memory to the SQL Server process, other important processes will hang the Server when a critical process fails to get memory due to...

This is because of the fact that your heap is small relative to the indexes and that SQL Server tries to keep the index pools closely knit, and in most...

Answer to Q1:

Merged replication is somewhat different to what you presume. The Merged replication allows to update the Primary server from the secondary when any change occurs in it. It...

You are surely wrong this time if you don't stick to a few peoples proposition. It has not been decided yet for yobibyte.

Reference - http://en.wikipedia.org/wiki/Yottabyte

Be careful of orphaned users......

When you restore your database, or even detach and attach the user databases, the old ids for the users will be kept, while the logins created...

Better you use the following statement -

DECLARE DB CURSOR

FOR SELECT [name]

FROM SYS.DATABASES

WHERE owner_sid<>0x01

FOR READ ONLY

DECLARE @DB_NAMEVARCHAR(100),

@STR_SQLVARCHAR(20),

@STR_DBVARCHAR(150)

OPEN DB

FETCH NEXT FROM DB INTO @DB_NAME

WHILE @@FETCH_STATUS=0

BEGIN

SET @STR_DB='USE ['+@DB_NAME+']'

SET @STR_SQL=' EXEC sp_updatestats'

EXEC(@STR_DB+@STR_SQL)

FETCH NEXT FROM...

If you are using SQL 2005 and above, you can go ahead, but for versions before 9.0, executing sp_updatestats resets the automatic UPDATE STATISTICS setting for all indexes and statistics...

We are always here to help you..........we love problems.........it lets us know more........and to add, Gila Monster is one of the best and cool headed I have seen out here.......for...

We are always here to help you..........we love problems.........it lets us know more........and to add, Gila Monster is one of the best and cool headed I have seen out here.......for...

Yeah....to change the collation property of the server you need to run setup once again, after backing up everything which are required.....

Well, you can always change the collation property of...

It seems what you require is to use SSIS (SQL Server Integration Services).....something similar to a DTS, as you had in SQL 2000

The situation seems to be as follows -

A database activity was active, which might have slowed down the server. It was very risky to restart the server, as some data...

You can try the SQL Tool belt from Redgate......and synchronize the databases if the schemas are almost similar....in case you want to do update selective changes........but be careful and take...

DO you want to overwrite the database?

Then I can help....

Sure...you can use SQL 2005 MS SSMS, but creating DTS packages and few other activities will get you into trouble......:hehe: