Recent content by ptheriault

Using sp_help_rev_logins would have been my suggestion. I don't think you have any other option. - Paul - Experience is the name every one gives to their mistakes.

Take a look at this post, it may be helpful. http://forums.bea.com/thread.jspa?threadID=400004068 xa_start is not a sql server procedure. - Paul - Experience is the name every one gives to their mistakes.

Have you checked weblogic? That is definetly a weblogic error. - Paul - Experience is the name every one gives to their mistakes.

Steve, You really shouldn't give out sysadmin admin rights to users or application logins. That is a very bad practice to get into. Did you delete the Built-in admin user? That login will make all the local server admins 'sa' in the database server. But only if you haven't deleted it or...

Well that gives you another option. I haven't used SAN replication as of yet, but I've heard good things about it and if you have a good SAN admin should be easy to set up. I think Denny could offer you more advice on that than I can. - Paul - Experience is the name every one gives to their...

Does the login have one of the following permissions? - Paul - Experience is the name every one gives to their mistakes.

If your requirement is one refresh a day then snap shot is what you want. It will script out the database and the data in each table and run the scripts where ever your reporting db is. So yes the data is static in that sense. So, if you schedule your snap shot for 12 AM. then your reporting...

If this is for 2005 this will show you the user roles. SELECT p.name, s.name as Role, create_date, modify_date , CASE WHEN is_disabled = 0 THEN 'Enabled' ELSE 'Disabled' END as Status FROM sys.server_principals p JOIN ( select...

http://www.sql-server-performance.com/articles/clustering/clustering_intro_p1.aspx - Paul - Experience is the name every one gives to their mistakes.

Given your new requirements I would definetly go with snap shot replication. With log shipping I believe the db must be left in a state of restoring, which means you can use the db for reports. Also, snap shot replication would have the least impact on performance if the snapshot can be run...

My first suggestion would be to take a serious look at your indexes. If you have a db that is 12 gb of data and 14 gb of indexes then you have way to many indexes! Believe it or not but to many indexes is a bad thing. They will kill your inserts. updates and deletes. What are the...

Connect to the server instance with SSMS (SQL Server Managment Studio). Drill down into the Security and open the account that you are having issues with. You will see security options on the first page. - Paul - Experience is the name every one gives to their mistakes.

Most likely your admin has set your account to enforce password policy and password expiration. Ask your DBA to confirm what policies he has in effect for your account. - Paul - Experience is the name every one gives to their mistakes.

You should post any questions you have about SSAS in this forum: forum960 - Paul - Experience is the name every one gives to their mistakes.

You need to change the name of the sql instances. You can't have a sql server of the same name on the network, its like having two pc's with the same IP. Look up sp_dropserver and sp_addserver in BOL. Here is a proc to rename a server. Create proc uspRenameServer @pNewName...