i would have thought that differences in collation are what is breaking your comparisons.....but if all the columns are the same collation as the database, i would think that that...

our shop thinks of DBA's as two different categories....there's development DBA's, which only need access to the databases in order to create schemas, write procs,review other developers code, etc.. That role...

when you changed your database collation, did you change all the existing columns too?

a temp solution would be like this:

select * from gmact where actnbr like '120%' collate Sql_Latin1_General_CP1253_greek_CI_AS

a permenant...

in order to do that, the account used to run SQL server would need to have network rights...so instead of the default of running as system, it would need to...

i looked in google groups and everyone who responded witht eh same error had instaleld the free copy, and then the production copy, which was technically a different version:

http://groups.google.com/group/microsoft.public.sqlserver.server/browse_frm/thread/cc9c2343aa5bdfee/bf12353373a242e4?lnk=st&q=The+Notification+Services+instance+encountered+an+error+in+one+of+its+components+and+must+stop.&rnum=1&hl=en#bf12353373a242e4

sounds...

post the query; most likely we can help tune it ; most likely the WHERE clause can be tuned to use SARG-able arguments, which will then use the proper indexes...

If you create an empty database, but make the space allocated 10 GIG, you'll need 10 GIG to restore that backup, even though the database might be empty, or much...

nice, concise example to show someone why float is not a good solution for moeny. Thanks!

after you've created your new filegroup, this script might help: it writes the sql statements you could use to move some of your indexes; i've used it just for regular...

wouldn't the sp need to be recompiled after the table is truncated, as the previous executtion plan would probably be invalid? i would think the proc is slow because of...

here's a script i've used to generate the SQLs needed to change collation of a database for the existing items alzdba mentioned above;

I wouldn't try to modify this to fiddle...

you should change your design a bit;

your update trigger should populate a table of emails to be sent, and a job that runs every minute or five minutes or whatever...

i believe the issue is related to the way oracle 10 handles BLOB and CLOB columns;

if we don't use the updated drivers that are part of the Ora10 client install,...

this might be of some help; what SP is on your i searched the KB and found something that references the dccc shrink command on a win2K SP2; fixed...

I like David McFarlands idea; just looping thru the text of the view/stored proc/whatever object, looking for specific strings is MUCH better than trying to write a dynamic string reader to...