Dear all,
what is the easiest way to rerun a set of time-scheduled subscriptions on a
report?
I need to rerun inflow on the Data Warehouse and rerun these reports.
BR,
BertProbabily the easiest way is to reshedule the subscription reports to a
couple of minutes so that it runs again.
Amarnath
"AS_haasrode" wrote:
> Dear all,
> what is the easiest way to rerun a set of time-scheduled subscriptions on a
> report?
> I need to rerun inflow on the Data Warehouse and rerun these reports.
> BR,
> Bert
>|||Dear Amarnath,
there are too many reports to reschedule. This is exactly what I was trying
to avoid.
I'd like to be able to retrigger the reports, once the nighly load has rerun
(overday).
Any other suggestions?
BR,
Bert
--
"Amarnath" wrote:
> Probabily the easiest way is to reshedule the subscription reports to a
> couple of minutes so that it runs again.
> Amarnath
> "AS_haasrode" wrote:
> > Dear all,
> >
> > what is the easiest way to rerun a set of time-scheduled subscriptions on a
> > report?
> > I need to rerun inflow on the Data Warehouse and rerun these reports.
> >
> > BR,
> > Bert
> >
> >
Showing posts with label dear. Show all posts
Showing posts with label dear. Show all posts
Tuesday, March 20, 2012
Tuesday, February 21, 2012
Re-Post - Process Information
Dear All,
Under Managment/Current Activity/Process Info you can see
all the users with connections to the system.
Here is the problem. A couple of users seem to have
multiple (10 or more) process ID's, all of them sleeping.
After a chat with them they said they were not in the
application, but the process was still being displayed.
My questions are then, should I be concerned, and why
aren't they closing automatically ?
Thanks
Peter> Dear All,
> Under Managment/Current Activity/Process Info you can see
> all the users with connections to the system.
> Here is the problem. A couple of users seem to have
> multiple (10 or more) process ID's, all of them sleeping.
> After a chat with them they said they were not in the
> application, but the process was still being displayed.
> My questions are then, should I be concerned, and why
> aren't they closing automatically ?
> Thanks
> Peter
--
Hi Peter,
It is possible that they are orphaned processes. Checkout this article:
INF: How to Troubleshoot Orphaned Connections in SQL Server
http://support.microsoft.com/?id=137983
Hope this helps,
Eric Crdenas
SQL Server senior support professional
Under Managment/Current Activity/Process Info you can see
all the users with connections to the system.
Here is the problem. A couple of users seem to have
multiple (10 or more) process ID's, all of them sleeping.
After a chat with them they said they were not in the
application, but the process was still being displayed.
My questions are then, should I be concerned, and why
aren't they closing automatically ?
Thanks
Peter> Dear All,
> Under Managment/Current Activity/Process Info you can see
> all the users with connections to the system.
> Here is the problem. A couple of users seem to have
> multiple (10 or more) process ID's, all of them sleeping.
> After a chat with them they said they were not in the
> application, but the process was still being displayed.
> My questions are then, should I be concerned, and why
> aren't they closing automatically ?
> Thanks
> Peter
--
Hi Peter,
It is possible that they are orphaned processes. Checkout this article:
INF: How to Troubleshoot Orphaned Connections in SQL Server
http://support.microsoft.com/?id=137983
Hope this helps,
Eric Crdenas
SQL Server senior support professional
Re-Post - Process Information
Dear All,
Under Managment/Current Activity/Process Info you can see
all the users with connections to the system.
Here is the problem. A couple of users seem to have
multiple (10 or more) process ID's, all of them sleeping.
After a chat with them they said they were not in the
application, but the process was still being displayed.
My questions are then, should I be concerned, and why
aren't they closing automatically ?
Thanks
Peter
> Dear All,
> Under Managment/Current Activity/Process Info you can see
> all the users with connections to the system.
> Here is the problem. A couple of users seem to have
> multiple (10 or more) process ID's, all of them sleeping.
> After a chat with them they said they were not in the
> application, but the process was still being displayed.
> My questions are then, should I be concerned, and why
> aren't they closing automatically ?
> Thanks
> Peter
Hi Peter,
It is possible that they are orphaned processes. Checkout this article:
INF: How to Troubleshoot Orphaned Connections in SQL Server
http://support.microsoft.com/?id=137983
Hope this helps,
Eric Crdenas
SQL Server senior support professional
Under Managment/Current Activity/Process Info you can see
all the users with connections to the system.
Here is the problem. A couple of users seem to have
multiple (10 or more) process ID's, all of them sleeping.
After a chat with them they said they were not in the
application, but the process was still being displayed.
My questions are then, should I be concerned, and why
aren't they closing automatically ?
Thanks
Peter
> Dear All,
> Under Managment/Current Activity/Process Info you can see
> all the users with connections to the system.
> Here is the problem. A couple of users seem to have
> multiple (10 or more) process ID's, all of them sleeping.
> After a chat with them they said they were not in the
> application, but the process was still being displayed.
> My questions are then, should I be concerned, and why
> aren't they closing automatically ?
> Thanks
> Peter
Hi Peter,
It is possible that they are orphaned processes. Checkout this article:
INF: How to Troubleshoot Orphaned Connections in SQL Server
http://support.microsoft.com/?id=137983
Hope this helps,
Eric Crdenas
SQL Server senior support professional
Re-Post - Process Information
Dear All,
Under Managment/Current Activity/Process Info you can see
all the users with connections to the system.
Here is the problem. A couple of users seem to have
multiple (10 or more) process ID's, all of them sleeping.
After a chat with them they said they were not in the
application, but the process was still being displayed.
My questions are then, should I be concerned, and why
aren't they closing automatically ?
Thanks
Peter> Dear All,
> Under Managment/Current Activity/Process Info you can see
> all the users with connections to the system.
> Here is the problem. A couple of users seem to have
> multiple (10 or more) process ID's, all of them sleeping.
> After a chat with them they said they were not in the
> application, but the process was still being displayed.
> My questions are then, should I be concerned, and why
> aren't they closing automatically ?
> Thanks
> Peter
--
Hi Peter,
It is possible that they are orphaned processes. Checkout this article:
INF: How to Troubleshoot Orphaned Connections in SQL Server
http://support.microsoft.com/?id=137983
Hope this helps,
--
Eric Cárdenas
SQL Server senior support professional
Under Managment/Current Activity/Process Info you can see
all the users with connections to the system.
Here is the problem. A couple of users seem to have
multiple (10 or more) process ID's, all of them sleeping.
After a chat with them they said they were not in the
application, but the process was still being displayed.
My questions are then, should I be concerned, and why
aren't they closing automatically ?
Thanks
Peter> Dear All,
> Under Managment/Current Activity/Process Info you can see
> all the users with connections to the system.
> Here is the problem. A couple of users seem to have
> multiple (10 or more) process ID's, all of them sleeping.
> After a chat with them they said they were not in the
> application, but the process was still being displayed.
> My questions are then, should I be concerned, and why
> aren't they closing automatically ?
> Thanks
> Peter
--
Hi Peter,
It is possible that they are orphaned processes. Checkout this article:
INF: How to Troubleshoot Orphaned Connections in SQL Server
http://support.microsoft.com/?id=137983
Hope this helps,
--
Eric Cárdenas
SQL Server senior support professional
REPOST - Moving from 7.0 to 2000
Dear All,
I have a database 4.2 gb of data, 50 view, 618 sp, 31
functions 92 tables, 10 with image columns and 27 jobs in
SQL Server 7.0.
As the title sugests I am migrating to 2000 and would like
some tips / help ect. I have read the Microsoft Guide, but
was wondering there any tips, help and more
importantly 'Do not do even if MS tells you too' would be
greatly appriciated.
A
Hi
Test, Test and Test your applications. Yes, there is SQL 7.0 compatability
mode, but there are small differences between how 7 and 2000 would do
something, even in that mode.
The basic migration is easy. Make sure that the objects are owned correctly,
make sure that there are no objects referring to objects that have been
removed/renamed.
I move 7.0's to 2000's on daily basis and it just works. Best is if you
move onto new hardware at the same time as you don't keep any legacy
configuration mistakes.
Regards
Mike
"Alice" wrote:
> Dear All,
> I have a database 4.2 gb of data, 50 view, 618 sp, 31
> functions 92 tables, 10 with image columns and 27 jobs in
> SQL Server 7.0.
> As the title sugests I am migrating to 2000 and would like
> some tips / help ect. I have read the Microsoft Guide, but
> was wondering there any tips, help and more
> importantly 'Do not do even if MS tells you too' would be
> greatly appriciated.
> A
>
|||Thanks for your reply, it has been very helpful.
Unfortunatly we are installing it on an existing Server so
I was wondering what are the common legacy configuration
problems ?
Thanks
>--Original Message--
>Hi
>Test, Test and Test your applications. Yes, there is SQL
7.0 compatability
>mode, but there are small differences between how 7 and
2000 would do
>something, even in that mode.
>The basic migration is easy. Make sure that the objects
are owned correctly,
>make sure that there are no objects referring to objects
that have been
>removed/renamed.
>I move 7.0's to 2000's on daily basis and it just works.
Best is if you
>move onto new hardware at the same time as you don't keep
any legacy[vbcol=seagreen]
>configuration mistakes.
>Regards
>Mike
>"Alice" wrote:
in[vbcol=seagreen]
like[vbcol=seagreen]
but[vbcol=seagreen]
be
>.
>
I have a database 4.2 gb of data, 50 view, 618 sp, 31
functions 92 tables, 10 with image columns and 27 jobs in
SQL Server 7.0.
As the title sugests I am migrating to 2000 and would like
some tips / help ect. I have read the Microsoft Guide, but
was wondering there any tips, help and more
importantly 'Do not do even if MS tells you too' would be
greatly appriciated.
A
Hi
Test, Test and Test your applications. Yes, there is SQL 7.0 compatability
mode, but there are small differences between how 7 and 2000 would do
something, even in that mode.
The basic migration is easy. Make sure that the objects are owned correctly,
make sure that there are no objects referring to objects that have been
removed/renamed.
I move 7.0's to 2000's on daily basis and it just works. Best is if you
move onto new hardware at the same time as you don't keep any legacy
configuration mistakes.
Regards
Mike
"Alice" wrote:
> Dear All,
> I have a database 4.2 gb of data, 50 view, 618 sp, 31
> functions 92 tables, 10 with image columns and 27 jobs in
> SQL Server 7.0.
> As the title sugests I am migrating to 2000 and would like
> some tips / help ect. I have read the Microsoft Guide, but
> was wondering there any tips, help and more
> importantly 'Do not do even if MS tells you too' would be
> greatly appriciated.
> A
>
|||Thanks for your reply, it has been very helpful.
Unfortunatly we are installing it on an existing Server so
I was wondering what are the common legacy configuration
problems ?
Thanks
>--Original Message--
>Hi
>Test, Test and Test your applications. Yes, there is SQL
7.0 compatability
>mode, but there are small differences between how 7 and
2000 would do
>something, even in that mode.
>The basic migration is easy. Make sure that the objects
are owned correctly,
>make sure that there are no objects referring to objects
that have been
>removed/renamed.
>I move 7.0's to 2000's on daily basis and it just works.
Best is if you
>move onto new hardware at the same time as you don't keep
any legacy[vbcol=seagreen]
>configuration mistakes.
>Regards
>Mike
>"Alice" wrote:
in[vbcol=seagreen]
like[vbcol=seagreen]
but[vbcol=seagreen]
be
>.
>
REPOST - Moving from 7.0 to 2000
Dear All,
I have a database 4.2 gb of data, 50 view, 618 sp, 31
functions 92 tables, 10 with image columns and 27 jobs in
SQL Server 7.0.
As the title sugests I am migrating to 2000 and would like
some tips / help ect. I have read the Microsoft Guide, but
was wondering there any tips, help and more
importantly 'Do not do even if MS tells you too' would be
greatly appriciated.
AHi
Test, Test and Test your applications. Yes, there is SQL 7.0 compatability
mode, but there are small differences between how 7 and 2000 would do
something, even in that mode.
The basic migration is easy. Make sure that the objects are owned correctly,
make sure that there are no objects referring to objects that have been
removed/renamed.
I move 7.0's to 2000's on daily basis and it just works. Best is if you
move onto new hardware at the same time as you don't keep any legacy
configuration mistakes.
Regards
Mike
"Alice" wrote:
> Dear All,
> I have a database 4.2 gb of data, 50 view, 618 sp, 31
> functions 92 tables, 10 with image columns and 27 jobs in
> SQL Server 7.0.
> As the title sugests I am migrating to 2000 and would like
> some tips / help ect. I have read the Microsoft Guide, but
> was wondering there any tips, help and more
> importantly 'Do not do even if MS tells you too' would be
> greatly appriciated.
> A
>|||Thanks for your reply, it has been very helpful.
Unfortunatly we are installing it on an existing Server so
I was wondering what are the common legacy configuration
problems ?
Thanks
>--Original Message--
>Hi
>Test, Test and Test your applications. Yes, there is SQL
7.0 compatability
>mode, but there are small differences between how 7 and
2000 would do
>something, even in that mode.
>The basic migration is easy. Make sure that the objects
are owned correctly,
>make sure that there are no objects referring to objects
that have been
>removed/renamed.
>I move 7.0's to 2000's on daily basis and it just works.
Best is if you
>move onto new hardware at the same time as you don't keep
any legacy
>configuration mistakes.
>Regards
>Mike
>"Alice" wrote:
>> Dear All,
>> I have a database 4.2 gb of data, 50 view, 618 sp, 31
>> functions 92 tables, 10 with image columns and 27 jobs
in
>> SQL Server 7.0.
>> As the title sugests I am migrating to 2000 and would
like
>> some tips / help ect. I have read the Microsoft Guide,
but
>> was wondering there any tips, help and more
>> importantly 'Do not do even if MS tells you too' would
be
>> greatly appriciated.
>> A
>>
>.
>
I have a database 4.2 gb of data, 50 view, 618 sp, 31
functions 92 tables, 10 with image columns and 27 jobs in
SQL Server 7.0.
As the title sugests I am migrating to 2000 and would like
some tips / help ect. I have read the Microsoft Guide, but
was wondering there any tips, help and more
importantly 'Do not do even if MS tells you too' would be
greatly appriciated.
AHi
Test, Test and Test your applications. Yes, there is SQL 7.0 compatability
mode, but there are small differences between how 7 and 2000 would do
something, even in that mode.
The basic migration is easy. Make sure that the objects are owned correctly,
make sure that there are no objects referring to objects that have been
removed/renamed.
I move 7.0's to 2000's on daily basis and it just works. Best is if you
move onto new hardware at the same time as you don't keep any legacy
configuration mistakes.
Regards
Mike
"Alice" wrote:
> Dear All,
> I have a database 4.2 gb of data, 50 view, 618 sp, 31
> functions 92 tables, 10 with image columns and 27 jobs in
> SQL Server 7.0.
> As the title sugests I am migrating to 2000 and would like
> some tips / help ect. I have read the Microsoft Guide, but
> was wondering there any tips, help and more
> importantly 'Do not do even if MS tells you too' would be
> greatly appriciated.
> A
>|||Thanks for your reply, it has been very helpful.
Unfortunatly we are installing it on an existing Server so
I was wondering what are the common legacy configuration
problems ?
Thanks
>--Original Message--
>Hi
>Test, Test and Test your applications. Yes, there is SQL
7.0 compatability
>mode, but there are small differences between how 7 and
2000 would do
>something, even in that mode.
>The basic migration is easy. Make sure that the objects
are owned correctly,
>make sure that there are no objects referring to objects
that have been
>removed/renamed.
>I move 7.0's to 2000's on daily basis and it just works.
Best is if you
>move onto new hardware at the same time as you don't keep
any legacy
>configuration mistakes.
>Regards
>Mike
>"Alice" wrote:
>> Dear All,
>> I have a database 4.2 gb of data, 50 view, 618 sp, 31
>> functions 92 tables, 10 with image columns and 27 jobs
in
>> SQL Server 7.0.
>> As the title sugests I am migrating to 2000 and would
like
>> some tips / help ect. I have read the Microsoft Guide,
but
>> was wondering there any tips, help and more
>> importantly 'Do not do even if MS tells you too' would
be
>> greatly appriciated.
>> A
>>
>.
>
REPOST - Moving from 7.0 to 2000
Dear All,
I have a database 4.2 gb of data, 50 view, 618 sp, 31
functions 92 tables, 10 with image columns and 27 jobs in
SQL Server 7.0.
As the title sugests I am migrating to 2000 and would like
some tips / help ect. I have read the Microsoft Guide, but
was wondering there any tips, help and more
importantly 'Do not do even if MS tells you too' would be
greatly appriciated.
AHi
Test, Test and Test your applications. Yes, there is SQL 7.0 compatability
mode, but there are small differences between how 7 and 2000 would do
something, even in that mode.
The basic migration is easy. Make sure that the objects are owned correctly,
make sure that there are no objects referring to objects that have been
removed/renamed.
I move 7.0's to 2000's on daily basis and it just works. Best is if you
move onto new hardware at the same time as you don't keep any legacy
configuration mistakes.
Regards
Mike
"Alice" wrote:
> Dear All,
> I have a database 4.2 gb of data, 50 view, 618 sp, 31
> functions 92 tables, 10 with image columns and 27 jobs in
> SQL Server 7.0.
> As the title sugests I am migrating to 2000 and would like
> some tips / help ect. I have read the Microsoft Guide, but
> was wondering there any tips, help and more
> importantly 'Do not do even if MS tells you too' would be
> greatly appriciated.
> A
>|||Thanks for your reply, it has been very helpful.
Unfortunatly we are installing it on an existing Server so
I was wondering what are the common legacy configuration
problems ?
Thanks
>--Original Message--
>Hi
>Test, Test and Test your applications. Yes, there is SQL
7.0 compatability
>mode, but there are small differences between how 7 and
2000 would do
>something, even in that mode.
>The basic migration is easy. Make sure that the objects
are owned correctly,
>make sure that there are no objects referring to objects
that have been
>removed/renamed.
>I move 7.0's to 2000's on daily basis and it just works.
Best is if you
>move onto new hardware at the same time as you don't keep
any legacy
>configuration mistakes.
>Regards
>Mike
>"Alice" wrote:
>
in[vbcol=seagreen]
like[vbcol=seagreen]
but[vbcol=seagreen]
be[vbcol=seagreen]
>.
>
I have a database 4.2 gb of data, 50 view, 618 sp, 31
functions 92 tables, 10 with image columns and 27 jobs in
SQL Server 7.0.
As the title sugests I am migrating to 2000 and would like
some tips / help ect. I have read the Microsoft Guide, but
was wondering there any tips, help and more
importantly 'Do not do even if MS tells you too' would be
greatly appriciated.
AHi
Test, Test and Test your applications. Yes, there is SQL 7.0 compatability
mode, but there are small differences between how 7 and 2000 would do
something, even in that mode.
The basic migration is easy. Make sure that the objects are owned correctly,
make sure that there are no objects referring to objects that have been
removed/renamed.
I move 7.0's to 2000's on daily basis and it just works. Best is if you
move onto new hardware at the same time as you don't keep any legacy
configuration mistakes.
Regards
Mike
"Alice" wrote:
> Dear All,
> I have a database 4.2 gb of data, 50 view, 618 sp, 31
> functions 92 tables, 10 with image columns and 27 jobs in
> SQL Server 7.0.
> As the title sugests I am migrating to 2000 and would like
> some tips / help ect. I have read the Microsoft Guide, but
> was wondering there any tips, help and more
> importantly 'Do not do even if MS tells you too' would be
> greatly appriciated.
> A
>|||Thanks for your reply, it has been very helpful.
Unfortunatly we are installing it on an existing Server so
I was wondering what are the common legacy configuration
problems ?
Thanks
>--Original Message--
>Hi
>Test, Test and Test your applications. Yes, there is SQL
7.0 compatability
>mode, but there are small differences between how 7 and
2000 would do
>something, even in that mode.
>The basic migration is easy. Make sure that the objects
are owned correctly,
>make sure that there are no objects referring to objects
that have been
>removed/renamed.
>I move 7.0's to 2000's on daily basis and it just works.
Best is if you
>move onto new hardware at the same time as you don't keep
any legacy
>configuration mistakes.
>Regards
>Mike
>"Alice" wrote:
>
in[vbcol=seagreen]
like[vbcol=seagreen]
but[vbcol=seagreen]
be[vbcol=seagreen]
>.
>
Subscribe to:
Posts (Atom)