Resolving the following SQL Server Replication error is easy enough, and is general linked to access to replication folders on the Distributor file-system, from the Subscriber Agent account.
The full error message will look something like this:
The process could not read file ‘
Sometimes when trying to initialize a subscription on a SQL Server database that is involved in a replication topology, you could run into the following error message:
Cannot reinitialize subscriptions of non-immediate_sync publications
Change database context to ‘[db-name]‘.
Error: 20159
A pretty nasty message that means very little.
While setting up SQL Server Replication (Transactional Replication to be specific), I had successfully created the Publication and the Subscriptions, but nothing was being replicated between the publisher SQL Server instance and the subscriber SQL Server instance.
When viewing the subscription details through the Replication Monitor tool, the subscription was not throwing an error, and hanging with the following message:
The initial snapshot for publication is not yet available.
In the post I will explain why this is appearing, and how to resolve the issue and generate the required Replication Snapshot.
Microsoft has been trying to leverage its Azure (SQL Cloud) platform for a while now through enhanced availability and performance, as well as creating a few “unexpected” connectors, such as the Hadoop to SQL DB Connector, which is now available as a beta in an Azure environment.
While trying to migrate my old SQL Server Integration Services (SSIS) packages from the legacy Package Deployment Model project to a Project Deployment Model one, I ran into the following error on some (not all) SSIS package after selecting it for import:
Object name ‘[object-name]‘ is not valid. Name cannot end with a whitespace.
This is a typical frustrating SSIS error message, uninformative and goes nowhere. Hopefully the tip here should help you get around the error in this particular situation.
With SQL Server 2012, Microsoft has released a major and much needed update to its SQL Server Integration Services, including features that enable much better manageability features, performance tracking (and SSIS performance tuning) features, as well as better (closer) integration with SQL Server Database Engine.
In this post I introduce the new features of Integration Services that are enabled through the new Project Deployment Model, as well as highlight some of the short-comings of this new technology, particularly with regard to Scale-Out and Distributed Processing.
Hi Sreehari,
SSIS service will run on a separate process...June 28, 6:30 pm by Links Naji
Hi,
Suppose my system has 8GB RAM and I have installed...June 28, 6:30 pm by sreehari
Any idea if we can use the keywordTokenizer along with stemming....August 2, 12:30 pm by kanishka
I think you have remarked some very interesting points...January 21, 1:06 pm by Johnc511
Hi, good article!
Can you help me with one thing.
I'm...August 13, 7:22 pm by Alex