0

I'd like to pull some data into SQL Server Express, from a high-current electrical test machine running SQL Server.

The first problem I'm experiencing is that I can't get replication setup, because SQL Server Enterprise Manager can't setup replication into "Local", which is what it thinks the local (default) instance is.

(I've set up publication, but apart from that, I won't be permitted to configure replication at the factory end.)

I'm not wed to any particular version of SQL Server Express.

Have I set up SQL Server Express wrong (do I need to uninstall and reinstall)? Or how do I get replication into a default instance? Or, how do I create a named instance in SQL Server Express?

I've edited the question to remove information about the high-current electrical test machine, because that is not subject of the question

Improve this question
6
  • Pretty sure that the SSEE default instance isn't the same as SS stackoverflow.com/questions/3586196/…
    – Dale K
    Commented Jan 22 at 2:17
  • 3
    By SS7 do you mean SQL Server 7.0? If so, mainstream support for that ended 20 years ago.
    – AlwaysLearning
    Commented Jan 22 at 3:52
  • Oh gosh haha, I thought OP meant signalling system 7 😂
    – Dale K
    Commented Jan 22 at 5:35
  • You won't be able to replicate from SQL Server 7 to any modern version of SQL Server Express. Can you clarify exactly what versions are running and what you're trying to acomplish?
    – David Browne - Microsoft
    Commented Jan 22 at 15:10
  • You are probably going to need an intermediate version of SQL Server to replicate both ways. I sincerely hope this machine is going to be on a walled off VLAN...
    – Charlieface
    Commented Jan 23 at 1:24

1 Answer 1

Reset to default
0

New Instance

Instances have to be individually installed. For some versions, you need original media to install more instances -- for some versions the on disk installer only supports removal (uninstallation).

"local" instance

Enterprise Manager just remembers the name you choose to use. 'Registered' instances are listed in the registry. When setting up replication can't use an alias, and Enterprise Manager is not willing to use multiple aliases, so you must 'unregister' the alias 'local' in Enterprise Manager, and 'register' the instance using its connection name. This is just Enterprise manager and the registry, so it doesn't break anything that's not repeatable.

Notes

To connect for replication, the two or three ends need to be compatible versions, must use matching connection methods (TCP, named pipes, whatever, sometimes using 'default' as the connection method does not work), and must not be blocked by firewall or version dependent security blocks put in place by MS.

Improve this answer

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.