we have 2 servers with similar tables and columns and indexes with fillfactor
0. My replication is very slow during daytime and comes to normal at night
times.when i check the reads and writes both are more that 90 % high but when
i check the page splits it shows nothing.what do i need to do to fasten my
replication.
Do i need to add fillfactor?
i didn't see any page splits though
Thanks
Pardhi
Message posted via http://www.droptable.com
If you have no page splits, then I'd start monitoring for blocking issues
during synchronization.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Paul i didn't see any blocking either
Paul Ibison wrote:
>If you have no page splits, then I'd start monitoring for blocking issues
>during synchronization.
>Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
Message posted via http://www.droptable.com
|||Then perhaps it's just one of the the usual processor/memory/disk access
issues. You could use profiler to monitor these counters and see if this is
the issue.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
Showing posts with label similar. Show all posts
Showing posts with label similar. Show all posts
Monday, March 26, 2012
Friday, February 24, 2012
File output
I have read an Oracle article about the content management system they implemented, and was wondering whether a similar thing was possible with SQL Server.
The system basically stored the content of articles etc. in the database, as well as revisions etc., a stored procedure then generated an html page from the database content, my guess is that this then updated any necessary pages containing links etc.
My question is basically whether SQL Server (or T-SQL to be more precise) includes the ability to output the contents of fields into a file, so that when an SP was called it would generate the HTML for a page and output it to a file on the server. Thus avoiding the need to generate a page every time a request is received.
Thanks,
PaulI can think of a few ways to do this. I don't know of anything built in to SQL Server to handle this.
Do you want to call the sp from within the SQL server or from the command line?
Do you want the ability to (re)build only one file at a time or rebuild all files?
Do you have any metadata on the file names and locations?
Post back or "E" me directly.|||The idea would be that the stored procedure could be called when a record is inserted, thus when someone writes content it then creates the HTML page.
My guess is that there would also be the need to then update any linked pages, so if you wanted a link on the home page, the home page would also be re-written.
Anyway, it was nothing more than a thought, and was curious as to how SQL Server might support this kind of functionality.
Paul
The system basically stored the content of articles etc. in the database, as well as revisions etc., a stored procedure then generated an html page from the database content, my guess is that this then updated any necessary pages containing links etc.
My question is basically whether SQL Server (or T-SQL to be more precise) includes the ability to output the contents of fields into a file, so that when an SP was called it would generate the HTML for a page and output it to a file on the server. Thus avoiding the need to generate a page every time a request is received.
Thanks,
PaulI can think of a few ways to do this. I don't know of anything built in to SQL Server to handle this.
Do you want to call the sp from within the SQL server or from the command line?
Do you want the ability to (re)build only one file at a time or rebuild all files?
Do you have any metadata on the file names and locations?
Post back or "E" me directly.|||The idea would be that the stored procedure could be called when a record is inserted, thus when someone writes content it then creates the HTML page.
My guess is that there would also be the need to then update any linked pages, so if you wanted a link on the home page, the home page would also be re-written.
Anyway, it was nothing more than a thought, and was curious as to how SQL Server might support this kind of functionality.
Paul
Sunday, February 19, 2012
file growth problem in 2005
I just had a problem similar to the one in this post on the MSDN forum
(however no resolution to it was posted).
http://forums.microsoft.com/MSDN/Sho...71057&SiteID=1
I have a database on a server hosting multiple other databases and only this
one had the issue. It's currently set to a limited growth of 200 mb with a 10
mb file growth. It was at 150 mb but needed to grow over the weekend to 160
mb. The client was experiencing Primary filegroup errors on the database.
When I checked the file growth, it had been changed to 1280 percent. Of
course there was not enough space to allow THAT much growth. ;-)
Please let me know if there is a known issue with SQL 2005 and this problem
and how to correct it.
Thanks!
Hi
You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
I am not sure if it would be related to the following although the results
seem to be the same:
http://lab.msdn.microsoft.com/produc...2-729b178a7fa0
John
"mp3nomad" wrote:
> I just had a problem similar to the one in this post on the MSDN forum
> (however no resolution to it was posted).
> http://forums.microsoft.com/MSDN/Sho...71057&SiteID=1
> I have a database on a server hosting multiple other databases and only this
> one had the issue. It's currently set to a limited growth of 200 mb with a 10
> mb file growth. It was at 150 mb but needed to grow over the weekend to 160
> mb. The client was experiencing Primary filegroup errors on the database.
> When I checked the file growth, it had been changed to 1280 percent. Of
> course there was not enough space to allow THAT much growth. ;-)
> Please let me know if there is a known issue with SQL 2005 and this problem
> and how to correct it.
> Thanks!
|||I think it looks like it may be the same or extremely similar problem.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
> I am not sure if it would be related to the following although the results
> seem to be the same:
> http://lab.msdn.microsoft.com/produc...2-729b178a7fa0
>
> John
> "mp3nomad" wrote:
|||Hi
I suggest that you log your own incident report and call PSS.
John
"mp3nomad" wrote:
[vbcol=seagreen]
> I think it looks like it may be the same or extremely similar problem.
> "John Bell" wrote:
(however no resolution to it was posted).
http://forums.microsoft.com/MSDN/Sho...71057&SiteID=1
I have a database on a server hosting multiple other databases and only this
one had the issue. It's currently set to a limited growth of 200 mb with a 10
mb file growth. It was at 150 mb but needed to grow over the weekend to 160
mb. The client was experiencing Primary filegroup errors on the database.
When I checked the file growth, it had been changed to 1280 percent. Of
course there was not enough space to allow THAT much growth. ;-)
Please let me know if there is a known issue with SQL 2005 and this problem
and how to correct it.
Thanks!
Hi
You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
I am not sure if it would be related to the following although the results
seem to be the same:
http://lab.msdn.microsoft.com/produc...2-729b178a7fa0
John
"mp3nomad" wrote:
> I just had a problem similar to the one in this post on the MSDN forum
> (however no resolution to it was posted).
> http://forums.microsoft.com/MSDN/Sho...71057&SiteID=1
> I have a database on a server hosting multiple other databases and only this
> one had the issue. It's currently set to a limited growth of 200 mb with a 10
> mb file growth. It was at 150 mb but needed to grow over the weekend to 160
> mb. The client was experiencing Primary filegroup errors on the database.
> When I checked the file growth, it had been changed to 1280 percent. Of
> course there was not enough space to allow THAT much growth. ;-)
> Please let me know if there is a known issue with SQL 2005 and this problem
> and how to correct it.
> Thanks!
|||I think it looks like it may be the same or extremely similar problem.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
> I am not sure if it would be related to the following although the results
> seem to be the same:
> http://lab.msdn.microsoft.com/produc...2-729b178a7fa0
>
> John
> "mp3nomad" wrote:
|||Hi
I suggest that you log your own incident report and call PSS.
John
"mp3nomad" wrote:
[vbcol=seagreen]
> I think it looks like it may be the same or extremely similar problem.
> "John Bell" wrote:
file growth problem in 2005
I just had a problem similar to the one in this post on the MSDN forum
(however no resolution to it was posted).
http://forums.microsoft.com/MSDN/Sh...271057&SiteID=1
I have a database on a server hosting multiple other databases and only this
one had the issue. It's currently set to a limited growth of 200 mb with a 1
0
mb file growth. It was at 150 mb but needed to grow over the weekend to 160
mb. The client was experiencing Primary filegroup errors on the database.
When I checked the file growth, it had been changed to 1280 percent. Of
course there was not enough space to allow THAT much growth. ;-)
Please let me know if there is a known issue with SQL 2005 and this problem
and how to correct it.
Thanks!Hi
You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
I am not sure if it would be related to the following although the results
seem to be the same:
http://lab.msdn.microsoft.com/produ...62-729b178a7fa0
John
"mp3nomad" wrote:
> I just had a problem similar to the one in this post on the MSDN forum
> (however no resolution to it was posted).
> http://forums.microsoft.com/MSDN/Sh...271057&SiteID=1
> I have a database on a server hosting multiple other databases and only th
is
> one had the issue. It's currently set to a limited growth of 200 mb with a
10
> mb file growth. It was at 150 mb but needed to grow over the weekend to 16
0
> mb. The client was experiencing Primary filegroup errors on the database.
> When I checked the file growth, it had been changed to 1280 percent. Of
> course there was not enough space to allow THAT much growth. ;-)
> Please let me know if there is a known issue with SQL 2005 and this proble
m
> and how to correct it.
> Thanks!|||I think it looks like it may be the same or extremely similar problem.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
> I am not sure if it would be related to the following although the results
> seem to be the same:
> http://lab.msdn.microsoft.com/produ...62-729b178a7fa0
>
> John
> "mp3nomad" wrote:
>|||Hi
I suggest that you log your own incident report and call PSS.
John
"mp3nomad" wrote:
[vbcol=seagreen]
> I think it looks like it may be the same or extremely similar problem.
> "John Bell" wrote:
>
(however no resolution to it was posted).
http://forums.microsoft.com/MSDN/Sh...271057&SiteID=1
I have a database on a server hosting multiple other databases and only this
one had the issue. It's currently set to a limited growth of 200 mb with a 1
0
mb file growth. It was at 150 mb but needed to grow over the weekend to 160
mb. The client was experiencing Primary filegroup errors on the database.
When I checked the file growth, it had been changed to 1280 percent. Of
course there was not enough space to allow THAT much growth. ;-)
Please let me know if there is a known issue with SQL 2005 and this problem
and how to correct it.
Thanks!Hi
You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
I am not sure if it would be related to the following although the results
seem to be the same:
http://lab.msdn.microsoft.com/produ...62-729b178a7fa0
John
"mp3nomad" wrote:
> I just had a problem similar to the one in this post on the MSDN forum
> (however no resolution to it was posted).
> http://forums.microsoft.com/MSDN/Sh...271057&SiteID=1
> I have a database on a server hosting multiple other databases and only th
is
> one had the issue. It's currently set to a limited growth of 200 mb with a
10
> mb file growth. It was at 150 mb but needed to grow over the weekend to 16
0
> mb. The client was experiencing Primary filegroup errors on the database.
> When I checked the file growth, it had been changed to 1280 percent. Of
> course there was not enough space to allow THAT much growth. ;-)
> Please let me know if there is a known issue with SQL 2005 and this proble
m
> and how to correct it.
> Thanks!|||I think it looks like it may be the same or extremely similar problem.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
> I am not sure if it would be related to the following although the results
> seem to be the same:
> http://lab.msdn.microsoft.com/produ...62-729b178a7fa0
>
> John
> "mp3nomad" wrote:
>|||Hi
I suggest that you log your own incident report and call PSS.
John
"mp3nomad" wrote:
[vbcol=seagreen]
> I think it looks like it may be the same or extremely similar problem.
> "John Bell" wrote:
>
file growth problem in 2005
I just had a problem similar to the one in this post on the MSDN forum
(however no resolution to it was posted).
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=271057&SiteID=1
I have a database on a server hosting multiple other databases and only this
one had the issue. It's currently set to a limited growth of 200 mb with a 10
mb file growth. It was at 150 mb but needed to grow over the weekend to 160
mb. The client was experiencing Primary filegroup errors on the database.
When I checked the file growth, it had been changed to 1280 percent. Of
course there was not enough space to allow THAT much growth. ;-)
Please let me know if there is a known issue with SQL 2005 and this problem
and how to correct it.
Thanks!Hi
You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
I am not sure if it would be related to the following although the results
seem to be the same
http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=4369ed03-a43f-4fb5-9962-729b178a7fa0
John
"mp3nomad" wrote:
> I just had a problem similar to the one in this post on the MSDN forum
> (however no resolution to it was posted).
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=271057&SiteID=1
> I have a database on a server hosting multiple other databases and only this
> one had the issue. It's currently set to a limited growth of 200 mb with a 10
> mb file growth. It was at 150 mb but needed to grow over the weekend to 160
> mb. The client was experiencing Primary filegroup errors on the database.
> When I checked the file growth, it had been changed to 1280 percent. Of
> course there was not enough space to allow THAT much growth. ;-)
> Please let me know if there is a known issue with SQL 2005 and this problem
> and how to correct it.
> Thanks!|||I think it looks like it may be the same or extremely similar problem.
"John Bell" wrote:
> Hi
> You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
> I am not sure if it would be related to the following although the results
> seem to be the same:
> http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=4369ed03-a43f-4fb5-9962-729b178a7fa0
>
> John
> "mp3nomad" wrote:
> > I just had a problem similar to the one in this post on the MSDN forum
> > (however no resolution to it was posted).
> >
> > http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=271057&SiteID=1
> >
> > I have a database on a server hosting multiple other databases and only this
> > one had the issue. It's currently set to a limited growth of 200 mb with a 10
> > mb file growth. It was at 150 mb but needed to grow over the weekend to 160
> > mb. The client was experiencing Primary filegroup errors on the database.
> > When I checked the file growth, it had been changed to 1280 percent. Of
> > course there was not enough space to allow THAT much growth. ;-)
> >
> > Please let me know if there is a known issue with SQL 2005 and this problem
> > and how to correct it.
> >
> > Thanks!|||Hi
I suggest that you log your own incident report and call PSS.
John
"mp3nomad" wrote:
> I think it looks like it may be the same or extremely similar problem.
> "John Bell" wrote:
> > Hi
> >
> > You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
> >
> > I am not sure if it would be related to the following although the results
> > seem to be the same:
> > http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=4369ed03-a43f-4fb5-9962-729b178a7fa0
> >
> >
> > John
> >
> > "mp3nomad" wrote:
> >
> > > I just had a problem similar to the one in this post on the MSDN forum
> > > (however no resolution to it was posted).
> > >
> > > http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=271057&SiteID=1
> > >
> > > I have a database on a server hosting multiple other databases and only this
> > > one had the issue. It's currently set to a limited growth of 200 mb with a 10
> > > mb file growth. It was at 150 mb but needed to grow over the weekend to 160
> > > mb. The client was experiencing Primary filegroup errors on the database.
> > > When I checked the file growth, it had been changed to 1280 percent. Of
> > > course there was not enough space to allow THAT much growth. ;-)
> > >
> > > Please let me know if there is a known issue with SQL 2005 and this problem
> > > and how to correct it.
> > >
> > > Thanks!
(however no resolution to it was posted).
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=271057&SiteID=1
I have a database on a server hosting multiple other databases and only this
one had the issue. It's currently set to a limited growth of 200 mb with a 10
mb file growth. It was at 150 mb but needed to grow over the weekend to 160
mb. The client was experiencing Primary filegroup errors on the database.
When I checked the file growth, it had been changed to 1280 percent. Of
course there was not enough space to allow THAT much growth. ;-)
Please let me know if there is a known issue with SQL 2005 and this problem
and how to correct it.
Thanks!Hi
You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
I am not sure if it would be related to the following although the results
seem to be the same
http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=4369ed03-a43f-4fb5-9962-729b178a7fa0
John
"mp3nomad" wrote:
> I just had a problem similar to the one in this post on the MSDN forum
> (however no resolution to it was posted).
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=271057&SiteID=1
> I have a database on a server hosting multiple other databases and only this
> one had the issue. It's currently set to a limited growth of 200 mb with a 10
> mb file growth. It was at 150 mb but needed to grow over the weekend to 160
> mb. The client was experiencing Primary filegroup errors on the database.
> When I checked the file growth, it had been changed to 1280 percent. Of
> course there was not enough space to allow THAT much growth. ;-)
> Please let me know if there is a known issue with SQL 2005 and this problem
> and how to correct it.
> Thanks!|||I think it looks like it may be the same or extremely similar problem.
"John Bell" wrote:
> Hi
> You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
> I am not sure if it would be related to the following although the results
> seem to be the same:
> http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=4369ed03-a43f-4fb5-9962-729b178a7fa0
>
> John
> "mp3nomad" wrote:
> > I just had a problem similar to the one in this post on the MSDN forum
> > (however no resolution to it was posted).
> >
> > http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=271057&SiteID=1
> >
> > I have a database on a server hosting multiple other databases and only this
> > one had the issue. It's currently set to a limited growth of 200 mb with a 10
> > mb file growth. It was at 150 mb but needed to grow over the weekend to 160
> > mb. The client was experiencing Primary filegroup errors on the database.
> > When I checked the file growth, it had been changed to 1280 percent. Of
> > course there was not enough space to allow THAT much growth. ;-)
> >
> > Please let me know if there is a known issue with SQL 2005 and this problem
> > and how to correct it.
> >
> > Thanks!|||Hi
I suggest that you log your own incident report and call PSS.
John
"mp3nomad" wrote:
> I think it looks like it may be the same or extremely similar problem.
> "John Bell" wrote:
> > Hi
> >
> > You may want to log this at http://lab.msdn.microsoft.com/productfeedback/
> >
> > I am not sure if it would be related to the following although the results
> > seem to be the same:
> > http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=4369ed03-a43f-4fb5-9962-729b178a7fa0
> >
> >
> > John
> >
> > "mp3nomad" wrote:
> >
> > > I just had a problem similar to the one in this post on the MSDN forum
> > > (however no resolution to it was posted).
> > >
> > > http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=271057&SiteID=1
> > >
> > > I have a database on a server hosting multiple other databases and only this
> > > one had the issue. It's currently set to a limited growth of 200 mb with a 10
> > > mb file growth. It was at 150 mb but needed to grow over the weekend to 160
> > > mb. The client was experiencing Primary filegroup errors on the database.
> > > When I checked the file growth, it had been changed to 1280 percent. Of
> > > course there was not enough space to allow THAT much growth. ;-)
> > >
> > > Please let me know if there is a known issue with SQL 2005 and this problem
> > > and how to correct it.
> > >
> > > Thanks!
Subscribe to:
Posts (Atom)