Automatically grow database

If the autogrow is set on a database primary file group
when does the server actually grow the file? Does it wait
for an out of space condition or is it automated?Yes, on reaching its current size it will grow by either a
percentage of the current size or as a fixed number of MB.
It will take the space on the Hard Disk up, so make sure
you have plenty of disk space.
J
>--Original Message--
>If the autogrow is set on a database primary file group
>when does the server actually grow the file? Does it
wait
>for an out of space condition or is it automated?
>.
>|||It is before an out of space condtion. But you can set up a job to automate
it with the ALTER DATABASE statement.
"Kirk" <anonymous@.discussions.microsoft.com> wrote in message
news:5ed001c3df71$7aa9c230$7d02280a@.phx.gbl...
> If the autogrow is set on a database primary file group
> when does the server actually grow the file? Does it wait
> for an out of space condition or is it automated?|||The reason I ask is that we have the primary file group to
autogrow at 100mb. We have a maintenance plan that runs
every Sunday. For the past 2 Sunday's the job has failed
due to out of space. There is plenty of space on the
drive for the file to grow. Not sure why the job is
failing on space issue. That is why I ask if it is on
error does it grow.|||Having autogrow is better than nothing. But better yet, don't leave it
solely for SQL Server. The better way is to size your db, forecast its
growth, and allocate space accordingly. Leave the autogrow on but keep
checking back whether there is need of growing again, and if needed, do it
manually at a not-so-busy time. Autogrow can take time so long that your
application may error out while waiting for the growth (though it's not
likely in your case of autogrow size).
Not sure what your problem is. You have a plan to grow the db file every
sunday? That doesn't sound right. What for job was failing? What's the
role of the maintenance plan in your problem?
<anonymous@.discussions.microsoft.com> wrote in message
news:126301c3df8b$67613d60$a001280a@.phx.gbl...
> The reason I ask is that we have the primary file group to
> autogrow at 100mb. We have a maintenance plan that runs
> every Sunday. For the past 2 Sunday's the job has failed
> due to out of space. There is plenty of space on the
> drive for the file to grow. Not sure why the job is
> failing on space issue. That is why I ask if it is on
> error does it grow.

Automatic deployment of report models

Hi all,
I have a group of models, and I'm looking for a way to automatically
get them to deploy to the test report server every day. The only way I
know to deploy is to build the models in Visual Studio and then deploy
them from Visual Studio. Are there other ways (command line solutions
perhaps) that will do this?
Thanks for any answers.
MattYou should be able to do this via the RS Web Service Interface.
Someone should write a utility that monitors a folder or folders and auto
deploy reports from there, that would be really useful
Jim.
"Mwob" wrote:
> Hi all,
> I have a group of models, and I'm looking for a way to automatically
> get them to deploy to the test report server every day. The only way I
> know to deploy is to build the models in Visual Studio and then deploy
> them from Visual Studio. Are there other ways (command line solutions
> perhaps) that will do this?
> Thanks for any answers.
> Matt
>|||I have written such a utility - it will also deploy all my RDL files in my
local folder structure to the report server. I just pass in two parameters
to my utility: The Report Server URL and the ROOT folder to create to dump
the reports into.
Saves me tons of time, especially with client deployments. :)
=-Chris
"Jim Breffni" <JimBreffni@.discussions.microsoft.com> wrote in message
news:E7EBD6CD-1A8F-4743-B2EB-026BEDEF1BB8@.microsoft.com...
> You should be able to do this via the RS Web Service Interface.
> Someone should write a utility that monitors a folder or folders and auto
> deploy reports from there, that would be really useful
> Jim.
>
> "Mwob" wrote:
>> Hi all,
>> I have a group of models, and I'm looking for a way to automatically
>> get them to deploy to the test report server every day. The only way I
>> know to deploy is to build the models in Visual Studio and then deploy
>> them from Visual Studio. Are there other ways (command line solutions
>> perhaps) that will do this?
>> Thanks for any answers.
>> Matt
>>|||Hi all,
Thanks very much for the replies. I started looking at the
ReportingServices2005 web services, and found a method called
"CreateModel" that looks like it might help, but I can't figure out how
to structure a call to this method, and how to authenticate etc...
There is a lack of examples on the web with this information. Its
slightly more complicated for me too because we also develop a custom
authentication extension that we'll have to cater for in the web
services calls.
Chris, any chance you could share your application or at least some
code that describes how its done.
Thanks!
Matt
Chris Conner wrote:
> I have written such a utility - it will also deploy all my RDL files in my
> local folder structure to the report server. I just pass in two parameters
> to my utility: The Report Server URL and the ROOT folder to create to dump
> the reports into.
> Saves me tons of time, especially with client deployments. :)
> =-Chris
> "Jim Breffni" <JimBreffni@.discussions.microsoft.com> wrote in message
> news:E7EBD6CD-1A8F-4743-B2EB-026BEDEF1BB8@.microsoft.com...
> > You should be able to do this via the RS Web Service Interface.
> >
> > Someone should write a utility that monitors a folder or folders and auto
> > deploy reports from there, that would be really useful
> >
> > Jim.
> >
> >
> >
> > "Mwob" wrote:
> >
> >> Hi all,
> >>
> >> I have a group of models, and I'm looking for a way to automatically
> >> get them to deploy to the test report server every day. The only way I
> >> know to deploy is to build the models in Visual Studio and then deploy
> >> them from Visual Studio. Are there other ways (command line solutions
> >> perhaps) that will do this?
> >>
> >> Thanks for any answers.
> >>
> >> Matt
> >>
> >>|||If would be great if you could share that code.|||Anyone?
I'm looking for a relatively simple example implementation of some code
using the web services to publish a report model.
Mwob wrote:
> Hi all,
> Thanks very much for the replies. I started looking at the
> ReportingServices2005 web services, and found a method called
> "CreateModel" that looks like it might help, but I can't figure out how
> to structure a call to this method, and how to authenticate etc...
> There is a lack of examples on the web with this information. Its
> slightly more complicated for me too because we also develop a custom
> authentication extension that we'll have to cater for in the web
> services calls.
> Chris, any chance you could share your application or at least some
> code that describes how its done.
> Thanks!
> Matt
>
> Chris Conner wrote:
> > I have written such a utility - it will also deploy all my RDL files in my
> > local folder structure to the report server. I just pass in two parameters
> > to my utility: The Report Server URL and the ROOT folder to create to dump
> > the reports into.
> >
> > Saves me tons of time, especially with client deployments. :)
> >
> > =-Chris
> >
> > "Jim Breffni" <JimBreffni@.discussions.microsoft.com> wrote in message
> > news:E7EBD6CD-1A8F-4743-B2EB-026BEDEF1BB8@.microsoft.com...
> > > You should be able to do this via the RS Web Service Interface.
> > >
> > > Someone should write a utility that monitors a folder or folders and auto
> > > deploy reports from there, that would be really useful
> > >
> > > Jim.
> > >
> > >
> > >
> > > "Mwob" wrote:
> > >
> > >> Hi all,
> > >>
> > >> I have a group of models, and I'm looking for a way to automatically
> > >> get them to deploy to the test report server every day. The only way I
> > >> know to deploy is to build the models in Visual Studio and then deploy
> > >> them from Visual Studio. Are there other ways (command line solutions
> > >> perhaps) that will do this?
> > >>
> > >> Thanks for any answers.
> > >>
> > >> Matt
> > >>
> > >>

auto switching a login

Hello Group,
I have a situation where one of my intranet web
sites has this error: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
What happens is that when you open the intranet site,
the user is normally logged in with their AD login.
This AD login is in a group which has permissions to the database.
The user will leave the web page open for say and hour or two. When they
come back to their desk and refresh their browser, they get the error.
is it possible the site logs in correctly but the sleeping process casues
the user to be force over to 'NT AUTHORITY\ANONYMOUS LOGON'? This user is n
ot
a valid user in our database. We do not user this user for any of our
permissions.
RichHere's a guess:
1. Your Intranet site stores the user's login information (i.e.
username) in a session variable
2. Your web server is configured to expire idle sessions after a
specific interval, in IIS the default is 20 minutes. When a session
expires, all variables associated with it are lost.
3. Your user leaves the site open for an hour without doing anything.
The session expires, losing their username from the session variables.
4. When your user refreshes their page, the page isn't checking for a
valid session, it blindly tries to connect to the database using the
username stored in the session variables, in this case nothing.
The proper fix for this is for the Intranet site to check for a valid
session, and throw up a "Session has expired" message, instead of
trying to connect to the database without a username.|||Hello Tracy,
thanks for the ideas. I forwarded them to my web guy but it seems he
already had thought of those ideas!
1. Your Intranet site stores the user's login information (i.e.
username) in a session variable
[me web guy said] I do use the session variable but my program has a
checking that will renew a session when it expires.
2. Your web server is configured to expire idle sessions after a
specific interval, in IIS the default is 20 minutes. When a session
expires, all variables associated with it are lost.
[me web guy said] I believed time is extended to be longer than 1 hour.
Not
sure how long but I think it’s more than an hour.
3. Your user leaves the site open for an hour without doing anything.
The session expires, losing their username from the session variables.
[me web guy said] Like I mentioned in #1, it’s automatically renewed.
4. When your user refreshes their page, the page isn't checking for a
valid session, it blindly tries to connect to the database using the
username stored in the session variables, in this case nothing.
[me web guy said] Same as #1
...nuts...
Rich
"Tracy McKibben" wrote:

> Here's a guess:
> 1. Your Intranet site stores the user's login information (i.e.
> username) in a session variable
> 2. Your web server is configured to expire idle sessions after a
> specific interval, in IIS the default is 20 minutes. When a session
> expires, all variables associated with it are lost.
> 3. Your user leaves the site open for an hour without doing anything.
> The session expires, losing their username from the session variables.
> 4. When your user refreshes their page, the page isn't checking for a
> valid session, it blindly tries to connect to the database using the
> username stored in the session variables, in this case nothing.
> The proper fix for this is for the Intranet site to check for a valid
> session, and throw up a "Session has expired" message, instead of
> trying to connect to the database without a username.
>

auto switching a login

Hello Group,
I have a situation where one of my intranet web
sites has this error: Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
What happens is that when you open the intranet site,
the user is normally logged in with their AD login.
This AD login is in a group which has permissions to the database.
The user will leave the web page open for say and hour or two. When they
come back to their desk and refresh their browser, they get the error.
is it possible the site logs in correctly but the sleeping process casues
the user to be force over to 'NT AUTHORITY\ANONYMOUS LOGON'? This user is not
a valid user in our database. We do not user this user for any of our
permissions.
RichHere's a guess:
1. Your Intranet site stores the user's login information (i.e.
username) in a session variable
2. Your web server is configured to expire idle sessions after a
specific interval, in IIS the default is 20 minutes. When a session
expires, all variables associated with it are lost.
3. Your user leaves the site open for an hour without doing anything.
The session expires, losing their username from the session variables.
4. When your user refreshes their page, the page isn't checking for a
valid session, it blindly tries to connect to the database using the
username stored in the session variables, in this case nothing.
The proper fix for this is for the Intranet site to check for a valid
session, and throw up a "Session has expired" message, instead of
trying to connect to the database without a username.|||Hello Tracy,
thanks for the ideas. I forwarded them to my web guy but it seems he
already had thought of those ideas!
1. Your Intranet site stores the user's login information (i.e.
username) in a session variable
[me web guy said] I do use the session variable but my program has a
checking that will renew a session when it expires.
2. Your web server is configured to expire idle sessions after a
specific interval, in IIS the default is 20 minutes. When a session
expires, all variables associated with it are lost.
[me web guy said] I believed time is extended to be longer than 1 hour. Not
sure how long but I think itâ's more than an hour.
3. Your user leaves the site open for an hour without doing anything.
The session expires, losing their username from the session variables.
[me web guy said] Like I mentioned in #1, itâ's automatically renewed.
4. When your user refreshes their page, the page isn't checking for a
valid session, it blindly tries to connect to the database using the
username stored in the session variables, in this case nothing.
[me web guy said] Same as #1
...nuts...
Rich
"Tracy McKibben" wrote:
> Here's a guess:
> 1. Your Intranet site stores the user's login information (i.e.
> username) in a session variable
> 2. Your web server is configured to expire idle sessions after a
> specific interval, in IIS the default is 20 minutes. When a session
> expires, all variables associated with it are lost.
> 3. Your user leaves the site open for an hour without doing anything.
> The session expires, losing their username from the session variables.
> 4. When your user refreshes their page, the page isn't checking for a
> valid session, it blindly tries to connect to the database using the
> username stored in the session variables, in this case nothing.
> The proper fix for this is for the Intranet site to check for a valid
> session, and throw up a "Session has expired" message, instead of
> trying to connect to the database without a username.
>