August 20, 2008 at 10:41 pm
i geneareted the query of MS sql server 2000 and executed in MS sql server 2005.
i am getting this warning while executing thw SQL in MS server 2005.
what can be done to resolve it.
Default bound to column.
Default bound to column.
Default bound to column.
ALso i am getting this isssue ,
Cannot add rows to sysdepends for the current object because it depends on the missing object 'dp_Getfrisection'. The object will still be created.
Cannot add rows to sysdepends for the current object because it depends on the missing object 'dbo.dp_Getgersection'. The object will still be created.
August 20, 2008 at 10:44 pm
What exactly is this query? Those error messages will appear if you are creating a stored procedure that makes calls to other stored procedures that do not exist.
MARCUS. Why dost thou laugh? It fits not with this hour.
TITUS. Why, I have not another tear to shed;
--Titus Andronicus, William Shakespeare
August 21, 2008 at 2:15 am
thiyaga4u (8/20/2008)
Default bound to column.
That's not a warning, it's an informational message. Somewhere in your script you're either binding a default to a column (sp_binddefault) or you're using a user-defined data type that has a bound default.
All it's saying is that the default has been bound.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 22, 2008 at 6:42 am
i just took the query from SQL 2000 and executed in SQL 2005.
Will it have any impact or lose of any datas becuase of this warning message.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply