Viewing 15 posts - 61 through 75 (of 89 total)
Thanks AlzDBA this is exactly what I needed.
November 17, 2008 at 4:14 am
I'm new at the whole index fragmentatation but have found that smaller tables may sometimes show increased fragmentation after rebuilding the index. Particularly lookup tables in my instance.
November 5, 2008 at 11:45 pm
Cool, thanks for the feedback!
November 5, 2008 at 10:31 am
On closer inspection it turns out that the SQL login on the problem server was actually a system user group and not a Domain group like on the rest of...
October 15, 2008 at 1:23 am
Thank you very much for this, this is exactly what i'm trying to accomplish.
:hehe:
August 11, 2008 at 6:08 am
Okay problem solved ...
came across this on someones blog which is the equivelant to the ALTER Authorisation in SQL 2005
SQL 2000::hehe:
EXEC dbName..sp_changedbowner 'sa';
August 6, 2008 at 10:42 am
Validating a subscription will only notify if there are problems but it will not fix anything.
(I'm still new at this so someone should probably confirm).
You might want to check your...
August 6, 2008 at 1:16 am
Thank you Chris.
The problem I have is this though:
CoreItem 1 should not be returned because at least one of it's SubItem (1 and 2) have matching categories. Even if CoreItem3...
July 30, 2008 at 3:17 am
Hi my apoligies for the test data ... i've modified it a bit.
I'm trying to identify which CoreItem has SubItems with categories which do not correspond to any of the...
July 30, 2008 at 1:06 am
noeld (7/17/2008)
Take a look at :
sp_removedbreplication @dbname = 'db_name'
Thanks for this tip ... I just recently came accross a scenario where other means to remove the replicated...
July 21, 2008 at 8:47 am
I ran EXEC sp_helpmergepublication to see what the details of the publication were and it returned a backward_comp_level of 40.
Now I'm really confused because that level is not listed by...
July 14, 2008 at 4:16 am
Came accross something rather strange.
I examined the setup of each subscriber and found that the subscribers that were not experiencing timeouts were on SQL 2000 sp3...
The performance is still slower...
July 14, 2008 at 3:43 am
My bad ... was pretty sure I read somewhere that log shipping could not be used with 2005 / 2000 replication.
In any case books online lists all the details ......
July 14, 2008 at 3:31 am
Yes it is, you will however be limited to the abilities SQL 2000 in terms of replication. For example i think log shipping is not available in 2000.
Cheers.
July 14, 2008 at 2:28 am
Viewing 15 posts - 61 through 75 (of 89 total)