SQL 2000 SP3a on W2K SP4 server. I've created a new database with only three
tables and set the Recovery Model to Simple. The reason being, these tables
are essentially "temp" tables who's data will be constantly deleted and
re-inserted. Since it is all calculated data, I have no need for recovery of
any kind. My problem is this: Even with the Recovery Model set to Simple,
the Transaction Log grows exponentially. This is a real problem for me since
these tables may be emptied and re-populated 1,500 times in one evening.
What recovery model should I use in this situation in order to keep the Log
file size under control? Or should I just run SHRINKDATABASE or some other
utility after each cleaning?
Hi
Keep your transactions short and sweet. If it is all one transaction, and
you update 10 million rows, you will need a lot of space.
Shrink DB will not help unless the transaction is committed or rolled back.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron Hinds" <__ron__dontspamme@.wedontlikespam_garageiq.com> wrote in message
news:O5ijLRPAGHA.3136@.TK2MSFTNGP15.phx.gbl...
> SQL 2000 SP3a on W2K SP4 server. I've created a new database with only
> three
> tables and set the Recovery Model to Simple. The reason being, these
> tables
> are essentially "temp" tables who's data will be constantly deleted and
> re-inserted. Since it is all calculated data, I have no need for recovery
> of
> any kind. My problem is this: Even with the Recovery Model set to Simple,
> the Transaction Log grows exponentially. This is a real problem for me
> since
> these tables may be emptied and re-populated 1,500 times in one evening.
> What recovery model should I use in this situation in order to keep the
> Log
> file size under control? Or should I just run SHRINKDATABASE or some other
> utility after each cleaning?
>
Showing posts with label model. Show all posts
Showing posts with label model. Show all posts
Sunday, March 11, 2012
"Simple" recovery model?
SQL 2000 SP3a on W2K SP4 server. I've created a new database with only three
tables and set the Recovery Model to Simple. The reason being, these tables
are essentially "temp" tables who's data will be constantly deleted and
re-inserted. Since it is all calculated data, I have no need for recovery of
any kind. My problem is this: Even with the Recovery Model set to Simple,
the Transaction Log grows exponentially. This is a real problem for me since
these tables may be emptied and re-populated 1,500 times in one evening.
What recovery model should I use in this situation in order to keep the Log
file size under control? Or should I just run SHRINKDATABASE or some other
utility after each cleaning?Hi
Keep your transactions short and sweet. If it is all one transaction, and
you update 10 million rows, you will need a lot of space.
Shrink DB will not help unless the transaction is committed or rolled back.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron Hinds" < __ron__dontspamme@.wedontlikespam_garagei
q.com> wrote in message
news:O5ijLRPAGHA.3136@.TK2MSFTNGP15.phx.gbl...
> SQL 2000 SP3a on W2K SP4 server. I've created a new database with only
> three
> tables and set the Recovery Model to Simple. The reason being, these
> tables
> are essentially "temp" tables who's data will be constantly deleted and
> re-inserted. Since it is all calculated data, I have no need for recovery
> of
> any kind. My problem is this: Even with the Recovery Model set to Simple,
> the Transaction Log grows exponentially. This is a real problem for me
> since
> these tables may be emptied and re-populated 1,500 times in one evening.
> What recovery model should I use in this situation in order to keep the
> Log
> file size under control? Or should I just run SHRINKDATABASE or some other
> utility after each cleaning?
>
tables and set the Recovery Model to Simple. The reason being, these tables
are essentially "temp" tables who's data will be constantly deleted and
re-inserted. Since it is all calculated data, I have no need for recovery of
any kind. My problem is this: Even with the Recovery Model set to Simple,
the Transaction Log grows exponentially. This is a real problem for me since
these tables may be emptied and re-populated 1,500 times in one evening.
What recovery model should I use in this situation in order to keep the Log
file size under control? Or should I just run SHRINKDATABASE or some other
utility after each cleaning?Hi
Keep your transactions short and sweet. If it is all one transaction, and
you update 10 million rows, you will need a lot of space.
Shrink DB will not help unless the transaction is committed or rolled back.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron Hinds" < __ron__dontspamme@.wedontlikespam_garagei
q.com> wrote in message
news:O5ijLRPAGHA.3136@.TK2MSFTNGP15.phx.gbl...
> SQL 2000 SP3a on W2K SP4 server. I've created a new database with only
> three
> tables and set the Recovery Model to Simple. The reason being, these
> tables
> are essentially "temp" tables who's data will be constantly deleted and
> re-inserted. Since it is all calculated data, I have no need for recovery
> of
> any kind. My problem is this: Even with the Recovery Model set to Simple,
> the Transaction Log grows exponentially. This is a real problem for me
> since
> these tables may be emptied and re-populated 1,500 times in one evening.
> What recovery model should I use in this situation in order to keep the
> Log
> file size under control? Or should I just run SHRINKDATABASE or some other
> utility after each cleaning?
>
"Simple" recovery model?
SQL 2000 SP3a on W2K SP4 server. I've created a new database with only three
tables and set the Recovery Model to Simple. The reason being, these tables
are essentially "temp" tables who's data will be constantly deleted and
re-inserted. Since it is all calculated data, I have no need for recovery of
any kind. My problem is this: Even with the Recovery Model set to Simple,
the Transaction Log grows exponentially. This is a real problem for me since
these tables may be emptied and re-populated 1,500 times in one evening.
What recovery model should I use in this situation in order to keep the Log
file size under control? Or should I just run SHRINKDATABASE or some other
utility after each cleaning?Hi
Keep your transactions short and sweet. If it is all one transaction, and
you update 10 million rows, you will need a lot of space.
Shrink DB will not help unless the transaction is committed or rolled back.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron Hinds" <__ron__dontspamme@.wedontlikespam_garageiq.com> wrote in message
news:O5ijLRPAGHA.3136@.TK2MSFTNGP15.phx.gbl...
> SQL 2000 SP3a on W2K SP4 server. I've created a new database with only
> three
> tables and set the Recovery Model to Simple. The reason being, these
> tables
> are essentially "temp" tables who's data will be constantly deleted and
> re-inserted. Since it is all calculated data, I have no need for recovery
> of
> any kind. My problem is this: Even with the Recovery Model set to Simple,
> the Transaction Log grows exponentially. This is a real problem for me
> since
> these tables may be emptied and re-populated 1,500 times in one evening.
> What recovery model should I use in this situation in order to keep the
> Log
> file size under control? Or should I just run SHRINKDATABASE or some other
> utility after each cleaning?
>
tables and set the Recovery Model to Simple. The reason being, these tables
are essentially "temp" tables who's data will be constantly deleted and
re-inserted. Since it is all calculated data, I have no need for recovery of
any kind. My problem is this: Even with the Recovery Model set to Simple,
the Transaction Log grows exponentially. This is a real problem for me since
these tables may be emptied and re-populated 1,500 times in one evening.
What recovery model should I use in this situation in order to keep the Log
file size under control? Or should I just run SHRINKDATABASE or some other
utility after each cleaning?Hi
Keep your transactions short and sweet. If it is all one transaction, and
you update 10 million rows, you will need a lot of space.
Shrink DB will not help unless the transaction is committed or rolled back.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Ron Hinds" <__ron__dontspamme@.wedontlikespam_garageiq.com> wrote in message
news:O5ijLRPAGHA.3136@.TK2MSFTNGP15.phx.gbl...
> SQL 2000 SP3a on W2K SP4 server. I've created a new database with only
> three
> tables and set the Recovery Model to Simple. The reason being, these
> tables
> are essentially "temp" tables who's data will be constantly deleted and
> re-inserted. Since it is all calculated data, I have no need for recovery
> of
> any kind. My problem is this: Even with the Recovery Model set to Simple,
> the Transaction Log grows exponentially. This is a real problem for me
> since
> these tables may be emptied and re-populated 1,500 times in one evening.
> What recovery model should I use in this situation in order to keep the
> Log
> file size under control? Or should I just run SHRINKDATABASE or some other
> utility after each cleaning?
>
Saturday, February 25, 2012
"model" system database transaction log
why would the transaction log of the model database have increased? this is a
template database what could be writing to it?
Obviously someone or some app has connected to the wrong db. Maybe someone
meant to use Tempdb and incorrectly chose Model instead.
Andrew J. Kelly SQL MVP
"Peter L." <PeterL@.discussions.microsoft.com> wrote in message
news:9B15D142-5FE8-4822-AAD2-57DDCE393B34@.microsoft.com...
> why would the transaction log of the model database have increased? this
> is a
> template database what could be writing to it?
>
template database what could be writing to it?
Obviously someone or some app has connected to the wrong db. Maybe someone
meant to use Tempdb and incorrectly chose Model instead.
Andrew J. Kelly SQL MVP
"Peter L." <PeterL@.discussions.microsoft.com> wrote in message
news:9B15D142-5FE8-4822-AAD2-57DDCE393B34@.microsoft.com...
> why would the transaction log of the model database have increased? this
> is a
> template database what could be writing to it?
>
"model" system database transaction log
why would the transaction log of the model database have increased? this is
a
template database what could be writing to it?Obviously someone or some app has connected to the wrong db. Maybe someone
meant to use Tempdb and incorrectly chose Model instead.
Andrew J. Kelly SQL MVP
"Peter L." <PeterL@.discussions.microsoft.com> wrote in message
news:9B15D142-5FE8-4822-AAD2-57DDCE393B34@.microsoft.com...
> why would the transaction log of the model database have increased? this
> is a
> template database what could be writing to it?
>
a
template database what could be writing to it?Obviously someone or some app has connected to the wrong db. Maybe someone
meant to use Tempdb and incorrectly chose Model instead.
Andrew J. Kelly SQL MVP
"Peter L." <PeterL@.discussions.microsoft.com> wrote in message
news:9B15D142-5FE8-4822-AAD2-57DDCE393B34@.microsoft.com...
> why would the transaction log of the model database have increased? this
> is a
> template database what could be writing to it?
>
"model" system database transaction log
why would the transaction log of the model database have increased? this is a
template database what could be writing to it?Obviously someone or some app has connected to the wrong db. Maybe someone
meant to use Tempdb and incorrectly chose Model instead.
--
Andrew J. Kelly SQL MVP
"Peter L." <PeterL@.discussions.microsoft.com> wrote in message
news:9B15D142-5FE8-4822-AAD2-57DDCE393B34@.microsoft.com...
> why would the transaction log of the model database have increased? this
> is a
> template database what could be writing to it?
>
template database what could be writing to it?Obviously someone or some app has connected to the wrong db. Maybe someone
meant to use Tempdb and incorrectly chose Model instead.
--
Andrew J. Kelly SQL MVP
"Peter L." <PeterL@.discussions.microsoft.com> wrote in message
news:9B15D142-5FE8-4822-AAD2-57DDCE393B34@.microsoft.com...
> why would the transaction log of the model database have increased? this
> is a
> template database what could be writing to it?
>
"Logon failed" when attempting to connect to cube.
Greetings. I am brand new to SRS, so please bear with me. I'm trying to
create a Report Model in SRS 2005 against an Analysis Services 2005 cube. I
am an admin on the AS box. I am using this tutorial:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rptsrvr9/html/8e5d2bd3-48ec-45f3-afee-6d86797c8f28.htm
I set up the data source, then I hit "generate model". I type in my model
name, hit "OK", and get the "Logon failed (rsLogonFailed)" message. I am
using "credentials supplied by the user running the report" dialog box with
the "Use as Windows..." checkbox checked. For good measure I have even added
myself to a cube Role with admin privelages. Alos, I can in fact browse and
manipulate the cube.
Any ideas?
TIA, ChrisRHi
I think the issue here is not the users priviliges in SSAS , rather
the priviliges in SSRS. Try using report manager to configure
permissions for the user in question .
Cheers
Shai
On Nov 20, 12:34 am, ChrisR <Chr...@.discussions.microsoft.com> wrote:
> Greetings. I am brand new to SRS, so please bear with me. I'm trying to
> create a Report Model in SRS 2005 against an Analysis Services 2005 cube. I
> am an admin on the AS box. I am using this tutorial:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rptsrvr9/html/8e5d2bd3-48ec-45f3-afee--6d86797c8f28.htm
> I set up the data source, then I hit "generate model". I type in my model
> name, hit "OK", and get the "Logon failed (rsLogonFailed)" message. I am
> using "credentials supplied by the user running the report" dialog box with
> the "Use as Windows..." checkbox checked. For good measure I have even added
> myself to a cube Role with admin privelages. Alos, I can in fact browse and
> manipulate the cube.
> Any ideas?
> TIA, ChrisR
create a Report Model in SRS 2005 against an Analysis Services 2005 cube. I
am an admin on the AS box. I am using this tutorial:
ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rptsrvr9/html/8e5d2bd3-48ec-45f3-afee-6d86797c8f28.htm
I set up the data source, then I hit "generate model". I type in my model
name, hit "OK", and get the "Logon failed (rsLogonFailed)" message. I am
using "credentials supplied by the user running the report" dialog box with
the "Use as Windows..." checkbox checked. For good measure I have even added
myself to a cube Role with admin privelages. Alos, I can in fact browse and
manipulate the cube.
Any ideas?
TIA, ChrisRHi
I think the issue here is not the users priviliges in SSAS , rather
the priviliges in SSRS. Try using report manager to configure
permissions for the user in question .
Cheers
Shai
On Nov 20, 12:34 am, ChrisR <Chr...@.discussions.microsoft.com> wrote:
> Greetings. I am brand new to SRS, so please bear with me. I'm trying to
> create a Report Model in SRS 2005 against an Analysis Services 2005 cube. I
> am an admin on the AS box. I am using this tutorial:
> ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/rptsrvr9/html/8e5d2bd3-48ec-45f3-afee--6d86797c8f28.htm
> I set up the data source, then I hit "generate model". I type in my model
> name, hit "OK", and get the "Logon failed (rsLogonFailed)" message. I am
> using "credentials supplied by the user running the report" dialog box with
> the "Use as Windows..." checkbox checked. For good measure I have even added
> myself to a cube Role with admin privelages. Alos, I can in fact browse and
> manipulate the cube.
> Any ideas?
> TIA, ChrisR
Saturday, February 11, 2012
"Custom" Report Model Data Source?
Hello,
Is this a true statement: "The only Data Sources available to a Report Model
are SQL Server 2000, SQL Server 2005, and SQL Server Analysis Services 2005"?
I had read somewhere that there was going to be an ability to specify a
"custom" query processors so that you could use data sources in addition to
the items listed above.
Thanks!I don't think so...
Since you can use ADO.Net every supported DataRpovider should work with
it... at least in local reports
"brianpmccullough" <bmccullough11@.comcast.net> wrote in message
news:2A5B524A-176B-4BD2-ACC2-75C9C3DDB2DA@.microsoft.com...
> Hello,
> Is this a true statement: "The only Data Sources available to a Report
> Model
> are SQL Server 2000, SQL Server 2005, and SQL Server Analysis Services
> 2005"?
> I had read somewhere that there was going to be an ability to specify a
> "custom" query processors so that you could use data sources in addition
> to
> the items listed above.
> Thanks!
>
Is this a true statement: "The only Data Sources available to a Report Model
are SQL Server 2000, SQL Server 2005, and SQL Server Analysis Services 2005"?
I had read somewhere that there was going to be an ability to specify a
"custom" query processors so that you could use data sources in addition to
the items listed above.
Thanks!I don't think so...
Since you can use ADO.Net every supported DataRpovider should work with
it... at least in local reports
"brianpmccullough" <bmccullough11@.comcast.net> wrote in message
news:2A5B524A-176B-4BD2-ACC2-75C9C3DDB2DA@.microsoft.com...
> Hello,
> Is this a true statement: "The only Data Sources available to a Report
> Model
> are SQL Server 2000, SQL Server 2005, and SQL Server Analysis Services
> 2005"?
> I had read somewhere that there was going to be an ability to specify a
> "custom" query processors so that you could use data sources in addition
> to
> the items listed above.
> Thanks!
>
Subscribe to:
Posts (Atom)
