After exporting the registered servers from SQL Server Management Studio’s “Registered Servers window” and then importing the exported list into a new machine. You may encounter the following error if passwords were stored against the servers… Registered Servers Key not valid for use in specified state. (System.Security) This
Copy assemblies into the correct reporting services folder When migrating to a new SQL server the barcodes were causing an issue, firstly because we lacked the barcode assemblies in the reporting services bin folder for the new version of Reporting Services that came with SQL server 2016. Finding the dlls
From SO post: https://stackoverflow.com/questions/200195/how-can-i-determine-the-status-of-a-job CREATE VIEW myschema.Admin_RunningSQLJobs AS SELECT job.NAME ,job.job_id ,job.originating_server ,activity.run_requested_date ,DATEDIFF(SECOND, activity.run_requested_date, GETDATE()) AS Elapsed FROM msdb.dbo.sysjobs_view job JOIN msdb.dbo.sysjobactivity activity ON job.
Working with the Dynamics GP inventory tables you will encounter the field named QTYTYPE a lot. This is usually seen with its partner LOCNCODE. Inventory in GP can reside in different locations (for example depots New York, London, Sidney). That location then is broken down further into five item types.
I’m frightened that one day this sample disappears, its from a SQL Server Central.com thread, Filling Bucketsoriginally posted by “ChrisM@work.” -- Originally from: -- http://www.sqlservercentral.com/Forums/Topic568498-338-1.aspx DECLARE @AmountToAllocate INT = 21 ;WITH Calculator AS ( SELECT BucketID, TotalSize, Amount, AmountLeftToAllocate = CASE WHEN @AmountToAllocate > (TotalSize
Linked server objects allow one SQL server to connect to another at the database engine level. A connection is defined when creating the linked server, including the credentials that should be used for that connection. As time passes, the challenge is knowing if that old linked server object is still
It is upgrade time, Dynamics GP does not like schema objects bound by replication during upgrades. During version updates some tables are copied dropped and recreated, depending on what changes have been made to the schema. If replication is left running on a Dynamics GP company during the upgrade, then
After moving Dynamics GP to a newly built server, using a back up and restore strategy, the Dynamics GP SQL replication kept causing problems. The following message drowned the error logs of the server. I ended up rebuilding replication configuration entirely to solve the issue, but there may be some