Master / Target Server
Apr 22, 2008Silly question, but why can you not setup a multi-server job and have that same server as a target? What's the rational behind this?
View 3 RepliesSilly question, but why can you not setup a multi-server job and have that same server as a target? What's the rational behind this?
View 3 RepliesI've installed SQL Server 2000 and applied SP3a. I see SP4 is available and fixes a lot of things. The only bit I am unsure about is section '5.3.2 Changes to Master/Target Server Configurations'
http://download.microsoft.com/download/1/b/d/1bdf5b78-584e-4de0-b36f-c44e06b0d2a3/ReadmeSql2k32sp4.htm#_5464_sql_server_agent_enhancements_705
"Before you apply SP4, you must complete several steps to upgrade your SQL Server 2000 master/target server configuration. The changes that are introduced with SP4 are not compatible with SQL Server 7.0 target servers, or with any servers not running SP3 or later. This is a change from the original SQL Server 2000 functionality. "
As I'm just starting out I don't even know what 'Master/Target Server' is. I'm only installing to my PC which is XP Pro SP2. Can I ignore this step and apply the patch or do I need to do as it states?
Thanks
I'm looking for a way to list the target servers associated with a master server. The reason is that we're moving to another master server, and I'd prefer not to move the targets manually.
I've got most of the T-SQL already (sp_msx_enlist, sp_add_jobserver), but I'd like a scripted solution instead of a wizard.
Sql Server 7 Standard EditionMy Server was renamed and the normal steps of reinstallingand running sp_dropserver and sp_addserver were followed.Everything seems to work fine but jobs from the master server.I did defect the server as a target server since it appeared as offlineanyway.On trying to re establish the status of the server as a target serverFailed to make "serverName" a target serverEnlist into Master Server "MasterServerName" Failed(Error 14262)Your insight is appreciatedVincento
View 3 Replies View RelatedI have several target servers defined, i have a job that needs to run in a serial fashion (ie.. 1 target at at time) if every target kicks off the job at the same time it's going to bog down the disk drives... can this be serialized? or do i need to write a special routine...
View 3 Replies View RelatedHi,
I have a problem using service broker, a send the message from server SSB1(initiator) and a receive this message on server SSB2(target), but I don't receive response to SSB1...
In my server SSB2 has this messages on Profiler:
- This message could not be delivered because it is a duplicate.
- Could not forward the message because forwarding is disabled in this SQL Server instance.
- The message could not be delivered because it could not be classified. Enable broker message classification trace to see the reason for the failure.
Message from SSB1 Profiler:
- This message was dropped because it could not be dispatched on time. State: 1
And the messages not end in both servers
Tks
Fernando Bueno
I'm not even sure this is possible but I'm using MERGE in a process that has 3 source tables (the process steps through each source table sequentially) and I need to delete from the Target database occasionally.
My current code is
sqlMerge = "MERGE " + TableName + " AS target USING @CData AS source" +
" ON target.TotRsp = source.TotRsp AND target.ClientRef = source.ClientRef AND target.dbPatID = source.dbPatID" +
" WHEN MATCHED THEN" +
" UPDATE SET dbPatFirstName = source.dbPatFirstName, dbPatLastName = source.dbPatLastName,
[Code] ....
The Target db data is made up from several different clients and when the MERGE runs it uses TotRsp, ClientRef and dbPatID to uniquely match a source row to the target row and if no match it inserts the source row.
My problem is that when this runs with Source A first, it will delete all merged data from Source B & C. Then when Source B runs it will insert all Source B data but delete all from A & C and so on.
Is there way that that I can include additional clauses into NOT MATCHED BY SOURCE THEN so it knows only to delete when data has come from say Source A. Once the data is in the target table there is no reference to which source table it came from tho.
If there isn't a solution I suppose I could always add an extra column to the target db to indicate which source it came from and then have something like
NOT MATCHED BY SOURCE AND t.Source = 'SourceA'.
That's quite a bit of work my end to do that tho so I'd like to be sure it works.
I was able to build and Preview the report, but ran into an issue when trying to deploy the report that I created. After reviewing various postings on this issue, I still can't seem to get past the issue.
Currently running SQL 2014 Developer Edition, SQL Server Data Tools for VS 2013, and O/S Windows 8.1 all on the laptop. I followed the video and left the default value of LocalHostReportServer. System said LocalhostReport Server could not be found.
I went to SQL Configuration Manager and tried using the Logon as the URL. Still received the same error.
I went to Reporting Services Configuration Manager and used the URL, still received the same error.
Regarding Snapshot replication....
If I have 200 tables on my source DB and 100 tables on my target DB... and I set up a publication w/ just 1 article to be published....
Will the invocation of the snapshot/apply affect any tables on my target other than the article I'm replicating?
Hi, I am less of a technical but more of a analyst professional and right now investgating on various tools / options for the new conversion project I will be leading in insurance client. One of the tools that client want to use is SSIS but the source and target database is not on SQL server but plans are to build a staging SQL server database for transformation. Does SSID supports this kind of ETL process where both source and target system are non SQL servers.
Thanks,
H Gill
I have a table:
declare tableName table
(
uniqueid int identity(1,1),
id int,
starttime datetime2(0),
endtime datetime2(0),
parameter int
)
A stored procedure has new set of values for a given id. Sometimes the startime and endtime are the same, in which case I update the value of parameter. Sometimes I add a new time range (insert statement), and sometimes I delete a time range (delete statement).
I had a question on merge, with insert, delete and update and I got that resolved. However I have a different question regarding performance of the merge statement.
If my target table has hundreds of millions of records and I want to delete/update/insert a handful of records, will SQL server scan the entire target table? I can't have:
merge ( select * from tableName where id = 10 ) as target
using ...
and I can't have:
merge tableName as target
using [my query] as source on
source.id = target.id and
source.starttime = target.startime and
source.endtime = target.endtime
where target.id = 10
...
This means I cannot filter the set of rows in the target table to a handful of records where id = 10.
I am created a SSIS package to export data. I am exporting query data to a flat file to a different server. I tried to use the UNC path and it failed saying could not access the file. How can I create a SSIS package to export data from one server to another?
View 5 Replies View RelatedI have documentation in the form of extended properties for tables which are subscribers in a replication scheme. The documentation describes the tables in reference to their replication scheme. I don't want to apply them to the source and have them published.I can't apply the extended properties receiving the error, 'don't have permission' yet I am DB creator on all systems. The theory is that I can't modify the subscription. Which makes sense.Can I turn off the replication, apply the extended properties, then turn on replication without causing harm?
View 0 Replies View RelatedI have a SQL Server 2005 box that was moved from a domain environment to a non-domain environment and was never dropped from its original domain before moving over. Subsequently a new domain was created at the data center this SQL Server box now resides in. The machine was dropped from its old domain and joined to the new one.
All the while the service accounts were set to the local admin account. When I tried to start the Configuration Manager I got the message "Connection to target machine could not be made in a timely fashion.". I read some blog entries and tried changing all the service accounts to Local System and the error message still came up.
All of the SQL Server services run fine. It is just this management console that I cannot open. I wasn't with this employer when this box was moved to the data center so I do not know if it worked prior and there isn't anyone here that could give me its history.
Any help would be appreciated.
Hi
I did a load testing and found the following observations:
1. The Memory:Pages/sec was crossing the limit beyond 20.
2. The Target Server Memory was always greater than Total Server Memory
Seeing the above data it seems to be memory pressure. But I found that AvailableMemory was always above 200 MB. Also Buffer Cache HitRatio was close to 99.99. What could be the reason for the above behavior?
I got a File with sales orders and their details.
Step 1. First I am filtering the Sales Order information and inserting it in my Sales Orders table.
Step 2.Then I am filtering the details from the sales Order and inserting them in the respective table.
My Problem is that the Sales Order File does not contain the Sales Order key (ID), this is generated by the SQL Server. How can get it in order to use it in the second step? I need it because it is a foreign key in the details table.
Any Idea?
Hi... I was hoping if someone could share me some thoughts with the issue that I am having at the moment.
Problem: When I run the package in my local machine and update local SS DB/table - new records writes OK in the table. BUT when I changed my destination meaning write record into another physical SS DB/table there is no INSERT data occurs. AND SO when I move/copy over that same package into another server (e.g. server that do not write record earlier) and run it locally IT WORKS fine too.
What I am trying to do is very simple - Add new records in a SS table using SSIS . I only care for new rows and not even changed rows.
Here is my logic -
1. Create Ole DB source to RemoteSERVER - using SELECT stmt
2. I have LoopUp component that will look for NEW records - Directs all rows that don't find match and redirect rows (error output).
3. Since I don't care for any rows that is matched in my lookup - I do nothing or I trash the rows
4. I send the error rows (NEW rows) into OleDB destination
RESULTS when I run the package locally and destination table is also local - WORKS FINE;
But when I run the package locally and destination table is in another Sserver (remote) - now rows is written.
The package is run thru BIDS manually so there is no sucurity restrictions attached to it.
I am not sure what I am missing. And I do not see error in my package either. It is not failing.
Thanks in advance!
I need to investigate about what happened to our production server at the last weekend.i restored it to another server which is development. I restored it under a name "old_master_2015_07_10".
But if I run a query
SELECT *
FROM [old_master_2015_07_10].[sys].[servers]
it actually selects from master.sys.servers, not from my old_master... In order to prove it, I created a linked server in this, development server, and if I run SELECT * FROM [old_master_2015_07_10].[sys].[servers], it selects it. And in database selection drop-down box I also selected old_ master_ 2015_07_10. What I think it apparently recognizes familiar names like sys.servers and redirects the query to the master.
What I can do to select really from old_master_2015_07_10 database? I already thought about renaming sys.servers to something different, but did not do it not to break something in master in case if SQL Server will run it in master as well.
Hi,We are planning to create a prod environment on our Dev server, bycreating a new named instance on DEV. Our prod server is running onsql enterprise edition 64bit and dev on SQl enterprise 32bit.Could we copy all the databases from prod server includingMaster,msdb,model onto our dev server, and bring up all the databases?Does Master store information about the version of SQl server?Thanks for your helpGG
View 1 Replies View RelatedI have never done this in a DR scenario before. What I used to do in SQL Server 2000 was apply the logins to a new installation of SQL 2000 then recover the application databases. I'm using 2005 now and I'm in a different mode where I would like to be able to recover the system (master, model, msdb) to a different server with the same SQL Server 2005 build ---- 9.0.3054. I'm following the procedures from Microsoft where they state to place the instance in single user mode first then invoke SQLCMD then perform the restore. Sounds simple enough.
C:> SQLCMD
> RESTORE DATABASE MASTER from DISK = 'Z:MINIDRmaster_backup_200804200315.bak'
The console is coming back with a message that the backup set holds a backup other than the existing master database. So I suppose that this cannot be done and is only intended for recovery on the same instance.
Any input/experience is appreciated.
Thanks.
So, I'm looking into using an MSX/TSX setup to help manage and monitor jobs, etc.
I took two test boxes and set one up as a Master and one as a Target and got it working...was able to push a job out and it ran and reported back, etc.
So, that's all great, but this was one small limited test. I'm curious to know if there are any gotchas that some of you have experienced that you would be willing to share with me to help prevent me from experiencing the same issues, etc.
I have about 40 instances that I'm considering using this MSX/TSX setup with, the remaining 15 instances would be monitored by something like Quest. Can a single MSX handle jobs on 40 instances? I already have maintenance plans and jobs set up on all the remote servers. Is there a way to transfer their ownership up to the MSX so they can be monitored from there? So far I haven't seen a way to do that.
*ponders*
Actually, one thing I just realized is that I could set up a job that looked for failed jobs. If I pushed that job out to all the TSX servers that could be used to alert me that something failed on a TSX box. That would actually be a great way to do it the more I think about it...Can anyone think of a reason why that is a bad idea?
Thanks!
Has anyone seen this issue before?
Msg 22026, Level 16, State 1, Line 0
The enlist operation failed (reason: SQLServerAgent Error: The target server cannot establish an encrypted connection to the master server 'MSXSERVERINSTANCE'. Make sure that the MsxEncryptChannelOptions registry subkey is set correctly on the target server.)
I did check the registry key (on all servers) and all of them have MsxEncryptChannelOptions set to the default of 2 (used this link as a guide - http://msdn.microsoft.com/en-us/library/ms365379.aspx).
I have setup the server MYMSXSERVERINSTANCE as the master and currently have 5 targets. This error occurs when I attempt to enlist the 6th server as a target.
Server information:
MSXSERVERINSTANCE - Product Version=9.00.3042.00; Product Level=SP2; Edition=Developer Edition; Engine Edition=3
TSXSERVER1INSTANCE - Product Version=9.00.3042.00; Product Level=SP2; Edition=Developer Edition; Engine Edition=3
TSXSERVER2INSTANCE - Product Version=9.00.3042.00; Product Level=SP2; Edition=Developer Edition; Engine Edition=3
TSXSERVER3INSTANCE - Product Version=9.00.3042.00; Product Level=SP2; Edition=Developer Edition; Engine Edition=3
TSXSERVER4INSTANCE - Product Version=9.00.3042.00; Product Level=SP2; Edition=Enterprise Edition; Engine Edition=3
TSXSERVER5INSTANCE - Product Version=9.00.3042.00; Product Level=SP2; Edition=Enterprise Edition; Engine Edition=3
TSXSERVER6INSTANCE - Product Version=9.00.3042.00; Product Level=SP2; Edition=Enterprise Edition (64-bit); Engine Edition=3
TSXSERVERS1-3 are 'nonproduction' level machines used for development and testing of our software. TSXSERVER4-5 are production servers (TSXSERVER5 is actually on an active/passive cluster and is the virtual name). TSXSERVER6 is a server that houses a day old copy of our production data for reporting purposes.
Now, TSXSERVER6 is the odd one here. It's a new server where we are pushing replicated data to for reporting purposes. Aside from the version of SQL Server being for 32-bit and 64-bit the only other difference is the OS:
MSXSERVER - Microsoft(R) Windows(R) Server 2003, Enterprise Edition
TSXSERVER1-3 - Microsoft(R) Windows(R) Server 2003, Standard Edition
TSXSERVER4-5 - Microsoft(R) Windows(R) Server 2003, Enterprise Edition
TSXSERVER6 - Microsoft(R) Windows(R) Server 2003 Enterprise x64 Edition
Has anyone ran into a situation like this? The obvious thing that comes to mind is that I might not be able to have a 64-bit version of SQL Server be a target to a 32-bit version of SQL Server. But I have been unable to locate any documentation stating this either way. Any suggestions on what to look at next... or better yet if you know the answer already let me know! :)
I have a full backup from ServerA. I then put ServerB in single user mode and try to restore the backup from ServerA. (both are identical servers but have different names)
[*- From command prompt using sqlcmd -*]
USE master
GO
RESTORE DATABASE master
FROM DISK = 'D:BACKUPSserverA.bak'
GO
Msg 3154, Level 16, State 4, Server MSSQL1, Line 1
The backup set holds a backup of a database other than the existing 'master' database.
Msg 3013, Level 16, State 1, Server MSSQL1, Line 1
RESTORE DATABASE is terminating abnormally.
Any ideas on forcing the restore through T-SQL? The restore works fine from a master backup from itself (ServerB).
Not sure where to post this. How do I restore the master database to a brand new server that has a different name than the server the master currently resides on? I am using SQL Server 2005.
View 1 Replies View RelatedHi All,
Here's my situation: I need to move several application db's to a new server. The current server is SQL 7.0 SP2, the new server will be SQL 7.0 SP3.
In order to avoid having the problems of mismatched logins and db user definitions, I'd like to restore the current master over the master that's created at install on the new server.
I was doing some testing of this by trying to restore the 7.0 SP2 master onto a SQL 7.0 DE edition and had some problems. (Obviously, this is not the exact scenario that I need to take place -- I want to restore standard edition to standard edition.)
Is restoring the master db from different service packs under 7.0 going to pose a problem? Is restoring the master db the best way to get around the logins issue when moving db's?
Thanks in advance for all replies.
Hi everybody.
Job was generated from from master server to run on target server
Target server does not exist any more
I want to delete this job but geeting error
"Error 14247 can't add ,update or delete job that generated from MSX server"
I have a server attached to a SAN, all user db's are on the SAN, master, tempdb, and msdb are on the local machine. We will be replacing the machine (not the SAN) to a newer sql server. Our plan was to create the new server with same name, deattach current user db's,backup master and msdb, then connect new server with same name an IP to SAN. I then wanted to restore the master and msdb db's to the new machine, and attach the user db's. We are running log shipping to a stand-by server in this configuration. I was thinking I could let last tran log backup and copy occur, and then let the last restore happen on the standby. I would then shut down the agent. Should I not be able to restore the MSDB and master to the new server (as long as all file folder locations are the same) and be ready to go? Or are there issues when restoring the Master and MSDB to a new server from a different server.
View 5 Replies View RelatedDoes anyone know how to move master db to a differetn drive instead of default c: drive in a named instance environment?
Thanks.
Rick
What considerations do I need to take into account if trying to enlist a server into a master server when (a) both instances are on different physical servers and the SQL Server and SQL Server Agent services run under different domain accounts?
The reason I ask is when attempting to create a master server through the SSMS wizard, I receive these errors:
Enlist TSX Progress
- Create MSXOperator (Success)
* Checking for an existing MSXOperator.
* Updating existing MSXOperator.
* Successfully updated MSXOperator.
- Make sure the Agent service for 'MYMSXINSTANCE' is running (Error)
Messages
* An exception occurred in SMO while trying to manage a service. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (mscorlib)
- Ensure the agent startup account for 'MYTSXINSTANCE' has rights to login as a target server (Error)
* Checking to see if the starup account for 'MYTSXINSTANCE' already exists.
Messages
* An exception occurred in SMO while trying to manage a service. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (mscorlib)
- Enlist 'MYTSXINSTANCE' into 'MYMSXINSTANCE' (Error)
* Enlisting target server 'MYTSXINSTANCE' with master server 'MYMSXINSTANCE'.
* Using new enlistment method.
Messages
* MSX enlist failed for JobServer 'MYTSXINSTANCE'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=MSX+enlist+JobServer&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
The enlist operation failed (reason: SQLServerAgent Error: Unable to connect to MSX 'MYMSXINSTANCE'.) (Microsoft SQL Server, Error: 22026)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.3042&EvtSrc=MSSQLServer&EvtID=22026&LinkId=20476
Now, the first two errors are what are puzzling me. I'm certain I can address the third and last error by making the accounts the SQL Server Agent services run as the necessary SQL permissions on each instance.
I've tried making NT AuthoritySYSTEM accounts on both servers, no luck. Any suggestions?
Hi All:
Please advise me about restore a master database from production to test server.
The reason to do this because I need to test and evaluate some login in master database.
I tried to restore master database to test server, but I got some errors regarding about user databases are not exists in test server. I don't want to restore user databases, I only need master database for evaluate user login.
Again thanks for your advice.
Hello,
I'm new to SQL and need help with a query. Not sure if this is the right place.
I have 2 tables, one MASTER and one DETAIL.
The MASTER table has a masterID, name and the DETAIL table has a detailID, masterID, and value columns.
I want to return a populated MASTER table with entries based on the DETAIL.value.
SELECT MASTER.*
FROM MASTER
WHERE DETAIL.value > 3
This is a simplified version of my problem. I can't figure out how to set the relationship between MASTER.masterID and DETAIL.masterID. If I do an INNER JOIN, the number of results are based on the number of DETAIL entries. I only want one entry per MASTER entry.
Hope this makes sense.
How can I do this?
GrkEngineer
I need information on steps to upgrade my current Master(MSX) server to a new server.
My MSX is a SQL 2K and it keep track of jobs in about 70 servers, some 2K and some 2K5.
Any ideas will help
Thanks
Jesus
As part of a project, I'm not allowed to use foreign keys, well can't. But I have a problem with this master detail relationship (and a very simple one too).
Tables to begin with:
Invoice:
invoiceid : bigint indentity autoincrement primarykey
Detail:
invoiceid: bigint - detailnumber:bigint - desc : char20
Okay - I want to set these two tables up such than when I create a new invoice, and subsequently get the new invoiceid, and I start to add detail records to the detail table, I want the detailnumber to autoincrement when I do an SQL Insert. Right now I have detailnumber as the primary key, so when you view the detail records, it looks like:
(invoiceid, detailnumber, desc) 1,1,text - 1,2,text - 1,3,text - 2,4, text on another invoice - 3,5, text
I want it to work like:
(invoiceid, detailnumber, desc) 1,1,text - 1,2,text - 1,3,text - 2,1, text on another invoice - 3,1, text
where the invoiceid and the detail number make up the primary key.
I seem to recall you could do this is PHP before it had foreign keys & such, and I'm completely drawing a blank on this. BTW - I'm using enterprise manager to set this up, but I can use QA with a sample script to acheive the same.
I realize this may be (and probably is) off-topic here, but I can't figure out where to ask.
Thanks in advance.