Viewing 13 posts - 1 through 13 (of 13 total)
Thank you for reply.
I checked and not found trigger on this table.
Table schema is exactly the same as scripted in previous mail.
The script runs successfully if I add GO between...
September 10, 2010 at 12:04 pm
table's script is:
CREATE TABLE [dbo].[EQ_Groups](
[EQ_GroupID] [int] NOT NULL,
[GroupType] [varchar](15) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[GroupCode] [varchar](15) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[Description] [varchar](80) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[SortOrder] [varchar](5) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
CONSTRAINT [PK_EQ_Groups] PRIMARY KEY...
September 10, 2010 at 5:56 am
July 6, 2010 at 5:31 am
Thanks for quick reply.
Table has clustered index already on publisher and subscriber both. The new index is non-clustered index.
March 6, 2009 at 1:51 pm
Use the DDL Trigger functionality:
CREATE TRIGGER ddl_trig_database
ON ALL SERVER
FOR CREATE_DATABASE
AS
--Add here code to notify dba team.
GO
March 5, 2009 at 2:35 pm
Verify that user 'DOM\my_sysadmin' is associated with Login 'DOM\my_sysadmin' in database in which sp is executing.
March 5, 2009 at 2:21 pm
The causing tables can be known from the deadlock details recorded by trace flage 1204. Then you can isolate the queries that are using that table.
March 2, 2009 at 6:18 am
Check the server's memory, disk, and processor status and if any of these is out of capacity, you may get the cause of issue. Some processes get suspended for long...
February 27, 2009 at 6:10 am
You can check the permission of that user using sys.database_permissions and sys.server_permissions catalog views. The output of these views may help to identify the root cause.
February 27, 2009 at 5:00 am
Know the processid of the the session that is using the database using sp_who2. Then kill that process then you may get access of that database.
February 27, 2009 at 4:36 am
There is no way to set priority for a process. But you can prevent other processes to take control on the table using trnasaction and lock hints. In your case,...
February 27, 2009 at 3:43 am
Whether your account is service account for SQL Server, it must be allowed to login to SQL Server by creating a windows login in SQL Server instance. Have your account...
February 27, 2009 at 2:33 am
Can you also provide the error desciption you got with error # 40. Also check the protocols (like Shared Memory, TCP/IP) configured on servers.
February 27, 2009 at 1:18 am
Viewing 13 posts - 1 through 13 (of 13 total)