Your new question:

doesn't have anything to do with your original question:

I just need...

Yes, 32GB is what my production Servers have. In this case I would do 16GB min SQL memory, 24GB max SQL memory and let the O/S manage the rest.

Why not just allocate 24GB to SQL Server and let the O/S manage the rest? I guess you don't really have a problem with 64GB of memory if your biggest...

You cannot do this. You will first need to create the other stored procedures in the database before they can be called. Stored procedures must exist on SQL Server before...

Actually I mispoke. I think it's a problem with your query. Try this and post results:

------------------------------ Get Stats on Indexes for a given table --------------------------------------------------------

Declare @object_ID int ,@dbid int

Select @object_ID...

You only have one clustered index on the table. two of the indexes just happened to be named with primary key nomenclature, but a clustered index doesn't even have to...

No problem. My experience using the tool has been positive. It identifies the objects and the problem in the specific object. However there is one caveate, the database must be...

This is what I use to find unused indexes on my SQL instances:

If Object_ID('dbo.Indexes_Unused_Select') is Null

Exec ( 'Create Proc dbo.Indexes_Unused_Select as Select 0')

Go

Alter Proc dbo.Indexes_Unused_Select

@Database sysname...

You can download the Microsoft SQL Server Upgrade Adviser. It will identify all of the objects, but you have to change them yourself.

http://www.microsoft.com/downloads/details.aspx?FamilyID=f5a6c5e9-4cd9-4e42-a21c-7291e7f0f852&displaylang=en

Meta data will be checked for existing objects which is why your only parse failure ocurrs when the table exists, but a column does not exist. As bteraberry suggested you...

This post should be under the security forum.

I think the issue is that the database master key is encrypted with the service master key, which is then used to encrypt...

Make sure both named pipes and tcp\ip are enabled on both servers. You can do this through the surface area configuration tool. I think you have to restart sql server...

On the server that has the database you want to replication (publish) execute the following:

use master

exec sp_replicationdboption @dbname = N'YOUR_DB_NAME', @optname = N'publish', @value = N'true'

Cool, I could use a script like that myself. One of the tricky things would be going accross servers, but I guess you would use linked servers for that. I...

You are not adding and account, but rather granting the account that already runs SQL server the right to "lock pages in memory." The reason this is important is that...