Viewing 6 posts - 1 through 7 (of 7 total)
It also occurred to me (now) that I could have scripted out all of the stored procedures into one file (or individual files) and searched for 'if exists' or 'drop...
September 14, 2011 at 10:05 am
Thanks for your comments, Gail. You nailed it.
We just didn't recognize why our SQL Compare appeared the same, until we could talk to clients and find out how these...
September 14, 2011 at 9:39 am
Solved!
We found that some client-vendor scripts were concatenated by clients. There was a missing 'go' at the end of one of them, and the next script dropped this view and...
September 14, 2011 at 9:32 am
No replication in this server. No mirroring. Nothing unusual. It is a named instance on this standalone host (no clustering).
Everything works, except saving (permanently) this view yesterday.
Mystery!...
September 14, 2011 at 8:43 am
cut an paste... the problem is with CREATE VIEW [usr1].[AIM_WO_COST] ... fails
not this version [usr1].[AIM_WO_COST2] = same content but resident, remains present and useable
September 13, 2011 at 4:44 pm
The view that fails is named usr1.AIM_WO_COST. No key words or invalid syntax.
It does not matter what schema owns it. We can create dbo.AIM_WO_COST and it will disappear.
If we...
September 13, 2011 at 4:41 pm
Viewing 6 posts - 1 through 7 (of 7 total)