Viewing 15 posts - 16 through 30 (of 174 total)
Yes, you were right. Transaction log remained the same size after the 'alter' statement:
ALTER TABLE dbo.TableName
ADD ColName INT CONSTRAINT DF_TableName_Init DEFAULT (0)
It's very strange, because one of our programmers...
January 9, 2007 at 2:04 pm
Thanks, I knew that there must be a way out. If I correctly understood, the key parts of this command are:
NOT NULL
CONSTRAINT DF_TableName_Init DEFAULT (0)
January 9, 2007 at 7:51 am
Have you tried to install AS SP4 on your personal PC? I believe this could be the problem
January 9, 2007 at 7:19 am
The situation has changed, now you have a SQL server named instance instead of default. Have you tried to create an TCP\IP server alias with the correct port number of the...
January 9, 2007 at 7:16 am
I had the same issue. Maybe this will help
http://support.microsoft.com/kb/822641
January 9, 2007 at 7:06 am
Jeff,
Thanks about the warning. The worst thing that could happen is that some nested procedure will not be noticed. I think the main goal is to identify the primary procedures,...
November 13, 2006 at 7:02 am
Jeff,
you are genius! Thank you very much.
Good Luck!
Vidas
November 12, 2006 at 12:15 pm
Colin,
are you telling me that the syscomments table will tell me what procedures had updated the x table particular column?
I have not a possibility to take a look at the...
November 10, 2006 at 5:40 am
Ok, from yours suggestions I see that there are two possible ways to accomplish my goal:
1. Trigger
2. Profiler
I've tried these both ways, but the drawback of the first is that I...
November 10, 2006 at 5:15 am
I couldn't agree with you. Trigger could be the best solution but how to get the procedure name, that updated the records? That appears the main problem to me for now
November 9, 2006 at 12:09 pm
John
>(2) You're putting yourself at risk from hackers if you don't change from the default port of 1433, especially if your server is web-facing
We accept connections from clients only in...
July 17, 2006 at 1:48 am
Yelena,
The messages "SQL server listening on xx.xx.xx.xx: 1433." and "SQL server listening on TCP, Shared Memory, Named Pipes." were in the SQL server log. I've checked that after reading http://support.microsoft.com/kb/328383/....
July 15, 2006 at 5:58 am
ALZBA
Do you have any links to official MS sites which could prove that fact?
July 14, 2006 at 11:51 am
John
Our cluster consist of two active nodes which holds two databases (one database per server). One of these DBs must be online 24x7. Users connect to it all the time...
July 14, 2006 at 11:48 am
John,
I guess my boss will not like me saying "you know it was one of those things" I've read a lot of Microsoft...
July 14, 2006 at 3:56 am
Viewing 15 posts - 16 through 30 (of 174 total)