Enabling Replication Question

Can I enable replication from a different server that has Enterprise
Manager install than the one that hosts the SQL database without any
problems or side effects?
I cannot enable replication from my server (Server A) hosting SQL
Server because the registration name is (local) instead of the server
name. Yes I know I can delete the registration and re-register it
with the server name BUT my ERP software vendor warns me by doing I
will break some of their core processing functionality because it
relies on the SQL Server registration name.
So to avoid this problem my though would be to enable replication from
(Server B) that has SQL Server Enterprise Manager installed and points
to Server A. My question is this - Can I successfully enable
replication through this process or will I encounter other problems or
create other issues?
I'm running SQL Server 2000.
Thanks for any information, comments or generally better ideas!Hi,
You can register server A in the Enterprise Manager on ANY machine
that has Enterprise Manager (and network access) -- including server B
-- and set up replication, or any other SQL administration tasks, on
server A.
Ken
On Feb 21, 5:31 pm, "dfrazell" <dfraz...@.estoneworks.com> wrote:
> Can I enable replication from a different server that has Enterprise
> Manager install than the one that hosts the SQL database without any
> problems or side effects?
> I cannot enable replication from my server (Server A) hosting SQL
> Server because the registration name is (local) instead of the server
> name. Yes I know I can delete the registration and re-register it
> with the server name BUT my ERP software vendor warns me by doing I
> will break some of their core processing functionality because it
> relies on the SQL Server registration name.
> So to avoid this problem my though would be to enable replication from
> (Server B) that has SQL Server Enterprise Manager installed and points
> to Server A. My question is this - Can I successfully enable
> replication through this process or will I encounter other problems or
> create other issues?
> I'm running SQL Server 2000.
> Thanks for any information, comments or generally better ideas!|||On Feb 21, 9:36 pm, "KenJ" <kenjohn...@.hotmail.com> wrote:[vbcol=seagreen]
> Hi,
> You can register server A in the Enterprise Manager on ANY machine
> that has Enterprise Manager (and network access) -- including server B
> -- and set up replication, or any other SQL administration tasks, on
> server A.
> Ken
> On Feb 21, 5:31 pm, "dfrazell" <dfraz...@.estoneworks.com> wrote:
>
>
>
>
>
So to clarify - I can enable replication on Server A from Server B
regardless of the SQL registration name of Server A without any side
effects?
Thanks - Dave|||As the server name of Server A will be the correct one when looking from
Server B's enterprise manager, I see no problems here provided you have a
sysadmin user. Some of the settings are local to the ServerA though (eg the
distribution working folder) so you might want to use a remote desktop as
well to set up the necessary share.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Enabling Replication Question

Can I enable replication from a different server that has Enterprise
Manager install than the one that hosts the SQL database without any
problems or side effects?
I cannot enable replication from my server (Server A) hosting SQL
Server because the registration name is (local) instead of the server
name. Yes I know I can delete the registration and re-register it
with the server name BUT my ERP software vendor warns me by doing I
will break some of their core processing functionality because it
relies on the SQL Server registration name.
So to avoid this problem my though would be to enable replication from
(Server B) that has SQL Server Enterprise Manager installed and points
to Server A. My question is this - Can I successfully enable
replication through this process or will I encounter other problems or
create other issues?
I'm running SQL Server 2000.
Thanks for any information, comments or generally better ideas!Hi,
You can register server A in the Enterprise Manager on ANY machine
that has Enterprise Manager (and network access) -- including server B
-- and set up replication, or any other SQL administration tasks, on
server A.
Ken
On Feb 21, 5:31 pm, "dfrazell" <dfraz...@.estoneworks.com> wrote:
> Can I enable replication from a different server that has Enterprise
> Manager install than the one that hosts the SQL database without any
> problems or side effects?
> I cannot enable replication from my server (Server A) hosting SQL
> Server because the registration name is (local) instead of the server
> name. Yes I know I can delete the registration and re-register it
> with the server name BUT my ERP software vendor warns me by doing I
> will break some of their core processing functionality because it
> relies on the SQL Server registration name.
> So to avoid this problem my though would be to enable replication from
> (Server B) that has SQL Server Enterprise Manager installed and points
> to Server A. My question is this - Can I successfully enable
> replication through this process or will I encounter other problems or
> create other issues?
> I'm running SQL Server 2000.
> Thanks for any information, comments or generally better ideas!|||On Feb 21, 9:36 pm, "KenJ" <kenjohn...@.hotmail.com> wrote:
> Hi,
> You can register server A in the Enterprise Manager on ANY machine
> that has Enterprise Manager (and network access) -- including server B
> -- and set up replication, or any other SQL administration tasks, on
> server A.
> Ken
> On Feb 21, 5:31 pm, "dfrazell" <dfraz...@.estoneworks.com> wrote:
> > Can I enable replication from a different server that has Enterprise
> > Manager install than the one that hosts the SQL database without any
> > problems or side effects?
> > I cannot enable replication from my server (Server A) hosting SQL
> > Server because the registration name is (local) instead of the server
> > name. Yes I know I can delete the registration and re-register it
> > with the server name BUT my ERP software vendor warns me by doing I
> > will break some of their core processing functionality because it
> > relies on the SQL Server registration name.
> > So to avoid this problem my though would be to enable replication from
> > (Server B) that has SQL Server Enterprise Manager installed and points
> > to Server A. My question is this - Can I successfully enable
> > replication through this process or will I encounter other problems or
> > create other issues?
> > I'm running SQL Server 2000.
> > Thanks for any information, comments or generally better ideas!
So to clarify - I can enable replication on Server A from Server B
regardless of the SQL registration name of Server A without any side
effects?
Thanks - Dave|||As the server name of Server A will be the correct one when looking from
Server B's enterprise manager, I see no problems here provided you have a
sysadmin user. Some of the settings are local to the ServerA though (eg the
distribution working folder) so you might want to use a remote desktop as
well to set up the necessary share.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com

Enabling MSSQLServerADHelper

I was installing application software that was trying to install SQL Server 2005 and received the following error message.

"Setup failed because Service MSSQLServerADHelper is disabled for the current hardware profile. Services must be set with the current Hardware Profile logon property profile enabled."

Simple fix for most but I do not know how to do what it asks.

Thanks, Bruce

Check this out as a good place to start:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q313939

Buck Woody

http://www.buckwoody.com

Enabling MSSQLServerADHelper

I was installing application software that was trying to install SQL Server 2005 and received the following error message.

"Setup failed because Service MSSQLServerADHelper is disabled for the current hardware profile. Services must be set with the current Hardware Profile logon property profile enabled."

Simple fix for most but I do not know how to do what it asks.

Thanks, Bruce

Check this out as a good place to start:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q313939

Buck Woody

http://www.buckwoody.com

Enabling full text search on existing sql server instance

Hi

I have an existing instance of sql express 2005 w/advanced services installed. When I installed I did not install full text search. Is there a way I can enable full text search on this existing instance?

Thanks

Try this:

sp_configure 'user instances enabled', '0'

sp_fulltext_database 'enable'

Then go ahead and try create your catalogs and indexes as normal.

Enable and disable case sensitivity

Hi,

I use a SQL Server 2000.

Is there a chance to change the case sensitivity option for a running instance of sql server?

I know, during the install process, i can activate the case sensitivity. But can I change this option on an already installed server (to case sensitiv or back)?

ThanksYes you can,
this option is called collation. You can set it diferently as default for each database at the same SQL server. Also it can be set for each collumn in each table separately.

Marf.

Originally posted by jenswitte
Hi,

I use a SQL Server 2000.

Is there a chance to change the case sensitivity option for a running instance of sql server?

I know, during the install process, i can activate the case sensitivity. But can I change this option on an already installed server (to case sensitiv or back)?

Thanks|||I think for that you will need to rebuild master ... which is not highly recommended.|||Originally posted by MarF
Yes you can,
this option is called collation. You can set it diferently as default for each database at the same SQL server. Also it can be set for each collumn in each table separately.

Marf.

Thanks! It worked. I changed the collation of a database from case insensitive to case sensitive and back.|||ummmm...huh?

Empty Warning box appears with only OK button (2 processes started) when I open Microsoft SQL se

Hello,

I'm new to SQL server 2005. I installed SQL server 2005 and had some problems with the original install. I therefore uninstalled SQL server 2005. Rebooted and than installed SQL server 2005 again. Everything appears to have installed correctly except for the fact that when I start SQL Server Management Suite I get 2 copies running in the foreground. The last copy of the SQL Server Management Suite shows a dialogue box that contain a warning sign (yellow triangle) with no text but an OK button is in the dialogue box. When I press the OK button, this instance of SQL Server Management Suite kills itself. The first instance is now given window focus and it brings up the "Connect to Server" dialogue box. I can connect to my local server and run a script to add columns to the database. But everytime I bring up SQL Server Management Suite, I always end up with 2 copies running and I have to hit the OK button to get rid of the second copy. Can anyone help me get ride of this annoying problem?

Hello,

I solved this problem! I installed windows XP Pro updates and one of the updates was the Update for .NET Framework 3.0 x86(KB932471). When I went to add/remove programs and removed this update, Microsoft SQL server management suite came up just like it is suppose to (only one instance running and the "Conncet to Server" Dialogue box is present.

JoAnn