Viewing 15 posts - 46 through 60 (of 210 total)
I could login to the SQLServerA from MachineB without any hindrance but when I try to connect to SQLServerA locally (From MachineA) then this throws eventid 18456. Can anyone discuss...
May 26, 2010 at 4:35 am
select distinct * from dupnames dup1
inner join dupnames dup2
on dup1.name = dup2.name
where dup1.id <> dup2. id
May 24, 2010 at 2:43 am
Try '"Example data to be imported"'
May 17, 2010 at 10:55 am
I think this was an issue with sql2k5 SP1. After that this error is no more. Could you tell your @@version Abhijeet?
February 25, 2010 at 3:29 am
It worked, Sturner. Thanks.
So the logic is that we need to use 'local' when we want the @@servername not to return the NULL value.
February 23, 2010 at 10:21 pm
Paul,
Can't we make the threshold change using GUI? Do I need to run sp_change_log_shipping_primary_database and sp_change_log_shipping_secondary_database?
February 19, 2010 at 6:05 am
Can anyone tell me how to change this setting please
February 18, 2010 at 5:52 am
Yes, clustered index can be added on another filegroup. But why this is not recommended to have the clustered index on another filegroup.
-Lk
February 17, 2010 at 4:49 am
True Gail. But what does allow_updates do?
February 16, 2010 at 6:42 am
My bad. Thanks Paul. /PAE SWITCH can be used with AMD as well.
February 16, 2010 at 5:00 am
I thing Service Pack = Many Hotfixes. Is there any good article that describes as how to apply the service pack or hotfixes?
February 16, 2010 at 3:30 am
If you are not using intel then you can't use /PAE switch for memory extension.
-Lk
February 16, 2010 at 1:42 am
Ok got it. in case this is sync (High availability) the there is no data loss and we can just issue ALTER DATABASE SET PARTNER FAILOVER.
But there is ofcourse...
January 28, 2010 at 7:20 am
Viewing 15 posts - 46 through 60 (of 210 total)