I'm using sqlserver 2005 developer edition.
Unlike databases, there appears to be no way, in Management Studio, to back
up ReportSever.
How is it done?
--
Regards,
Gary BlakelyHi Gary,
Thank you for your posting!
You could backup the ReportServer database as you backup other databases.
In the databases, right-click ReportServer and then click Back up. Then you
could backup the Reporty Server Database.
Here is an article for your reference:
Back Up Database (General Page)
http://msdn2.microsoft.com/en-us/library/ms183383(d=ide).aspx
Hope this will be helpful!
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label studio. Show all posts
Showing posts with label studio. Show all posts
Thursday, March 29, 2012
Tuesday, March 20, 2012
Background color differences between Visual Studio & Reporting Services
I'm trying to deploy a report to Reporting Services, but I've found that there's a behaviour difference Visual Studio and Reporting Services with the Matrix control for the subtotals.
For the background color for the "textbox" on the cells, I've used the folowing expression:
=Iif(Fields!ID__vs_YAGO.Value < 1, "Red"
,Iif(Fields!ID__vs_YAGO.Value < 1.02, "Yellow"
,"GreenYellow"))
The individual cells alternate colors, based on the value in the cell. In Visual Studio, the Subtotal cells also alternate colors (which is correct). But when the report is deployed to Reporting Services, The Subtotal cells have a transparent background. (Incorrect).
If I set the same expression into the background setting for the Subtotal cells, the expression is evaluated once for the entire row and the entire row has the same color (different Subtotal lines will alternate). This is the same in both Visual Studio and Reporting Services.
I'm using SP2, 2005 (32 bit for Reporting Services). To ensure full compatibility, I've editted / deployed the report all on the same machine.
Does anyone know of this problem and how to resolve it?
Additional: In testing the various output formats, it seems to be a bug in the HTML rendering engine. PDF amd TIFF work fine. I believe Excel export uses either part of the HTML rendering engine or pieces of the same code base.
P.S. I'm detecting other reporting differences between Visual Studio and Reporting Services, such as how "null key records" (from Analysis Services) are handled in groups. Is there a compatibility list published somewhere?
I've been having the same issues. I have been pulling my hair out for weeks.
Things to add:
I noticed that when deployed to Reporting Services, if you export to a TIFF or PDF, you will get the intended result. However, displayed on the web, and when exported to excel, it gives the above problems.
Background color differences between Visual Studio & Reporting Services
I'm trying to deploy a report to Reporting Services, but I've found that there's a behaviour difference Visual Studio and Reporting Services with the Matrix control for the subtotals.
For the background color for the "textbox" on the cells, I've used the folowing expression:
=Iif(Fields!ID__vs_YAGO.Value < 1, "Red"
,Iif(Fields!ID__vs_YAGO.Value < 1.02, "Yellow"
,"GreenYellow"))
The individual cells alternate colors, based on the value in the cell. In Visual Studio, the Subtotal cells also alternate colors (which is correct). But when the report is deployed to Reporting Services, The Subtotal cells have a transparent background. (Incorrect).
If I set the same expression into the background setting for the Subtotal cells, the expression is evaluated once for the entire row and the entire row has the same color (different Subtotal lines will alternate). This is the same in both Visual Studio and Reporting Services.
I'm using SP2, 2005 (32 bit for Reporting Services). To ensure full compatibility, I've editted / deployed the report all on the same machine.
Does anyone know of this problem and how to resolve it?
Additional: In testing the various output formats, it seems to be a bug in the HTML rendering engine. PDF amd TIFF work fine. I believe Excel export uses either part of the HTML rendering engine or pieces of the same code base.
P.S. I'm detecting other reporting differences between Visual Studio and Reporting Services, such as how "null key records" (from Analysis Services) are handled in groups. Is there a compatibility list published somewhere?
I've been having the same issues. I have been pulling my hair out for weeks.
Things to add:
I noticed that when deployed to Reporting Services, if you export to a TIFF or PDF, you will get the intended result. However, displayed on the web, and when exported to excel, it gives the above problems.
Sunday, March 11, 2012
Back Button in RS 2000?
Hello.
I'm developing reports in Reporting Services 2000 and Visual Studio 2003. I
have a "drill-through" report. Upon drilling through to the report, and then
clicking the back button to return to the main report, the report doesn't
even render. However, while developing the report and previewing it in VS
2003, there is a back button supplied there that works perfectly every time.
My question is this: is there a way to tell Reporting Services to include a
back button like the one in the report designer on the deployed report?
Alternatively, is there a way to provide a hyperlink in the drill-through
report that takes the user back to the original report (with all parameters
included in the link)?
Thanks!
JohnA small Back button is available in 2005. If it is not a parameter report
then it would have been easy, but since the main report is parameter based,
you can have a back button link and once you click; it comes back to the
main page and waits for parameter. So really it doesn;t serves your purpose.
But if the main page can wait for the input then you can use this method.
Amarnath
"JohnJohn" wrote:
> Hello.
> I'm developing reports in Reporting Services 2000 and Visual Studio 2003. I
> have a "drill-through" report. Upon drilling through to the report, and then
> clicking the back button to return to the main report, the report doesn't
> even render. However, while developing the report and previewing it in VS
> 2003, there is a back button supplied there that works perfectly every time.
> My question is this: is there a way to tell Reporting Services to include a
> back button like the one in the report designer on the deployed report?
> Alternatively, is there a way to provide a hyperlink in the drill-through
> report that takes the user back to the original report (with all parameters
> included in the link)?
> Thanks!
> John
I'm developing reports in Reporting Services 2000 and Visual Studio 2003. I
have a "drill-through" report. Upon drilling through to the report, and then
clicking the back button to return to the main report, the report doesn't
even render. However, while developing the report and previewing it in VS
2003, there is a back button supplied there that works perfectly every time.
My question is this: is there a way to tell Reporting Services to include a
back button like the one in the report designer on the deployed report?
Alternatively, is there a way to provide a hyperlink in the drill-through
report that takes the user back to the original report (with all parameters
included in the link)?
Thanks!
JohnA small Back button is available in 2005. If it is not a parameter report
then it would have been easy, but since the main report is parameter based,
you can have a back button link and once you click; it comes back to the
main page and waits for parameter. So really it doesn;t serves your purpose.
But if the main page can wait for the input then you can use this method.
Amarnath
"JohnJohn" wrote:
> Hello.
> I'm developing reports in Reporting Services 2000 and Visual Studio 2003. I
> have a "drill-through" report. Upon drilling through to the report, and then
> clicking the back button to return to the main report, the report doesn't
> even render. However, while developing the report and previewing it in VS
> 2003, there is a back button supplied there that works perfectly every time.
> My question is this: is there a way to tell Reporting Services to include a
> back button like the one in the report designer on the deployed report?
> Alternatively, is there a way to provide a hyperlink in the drill-through
> report that takes the user back to the original report (with all parameters
> included in the link)?
> Thanks!
> John
What is Query Analyzer's replacement in SQL Server 2005?
Both Query Analyzer and Enterprise Manager are gone from SQL Server 2005. In their place is a single tool, SQL Server Management Studio. This tool has most of the features of its predecessors, but with an upgraded UI and a lot of improved functionality. I think that most DBAs will find it to be a good upgrade. If you'd like more information on some of the new features with this tool, read my article on SQL Server Management Studio client tool enhancements.
http://searchsqlserver.techtarget.com/tip/1,289483,sid87_gci1146801,00.htmlPAE allows the OS to use more than 4GB of memory. AWE allows the
application to use more than 4GB.
Andrew J. Kelly SQL MVP
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:7D318157-43B8-49AD-9DF7-F38F6ABEEA03@.microsoft.com...
> guys,
> what is the difference between AWE and PAE?
|||for SQL server, shd i enable PAE or AWE? Can both be enabled at the same time?
"Andrew J. Kelly" wrote:
> PAE allows the OS to use more than 4GB of memory. AWE allows the
> application to use more than 4GB.
> --
> Andrew J. Kelly SQL MVP
>
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:7D318157-43B8-49AD-9DF7-F38F6ABEEA03@.microsoft.com...
>
>
|||AWE is a SQL Server setting (sp_configure) and PAE is an operating system setting (BOOT.INI). If you
want SQL Server to utilize > 4GB memory, you need both settings.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:82A723DF-8EEA-431B-8669-79146E1DCA1D@.microsoft.com...[vbcol=seagreen]
> for SQL server, shd i enable PAE or AWE? Can both be enabled at the same time?
> "Andrew J. Kelly" wrote:
|||in that case...in a server with 5G of ram
should i put the /AWE /PAE swith in the same line in the boot.ini?
For the OS, i can see under system mgmt that 5G is enabled. How abt for sql?
how do i check it has 5G? Also, is there any significant on it? The
performance shd be better i suppose
Thank you
"Tibor Karaszi" wrote:
> AWE is a SQL Server setting (sp_configure) and PAE is an operating system setting (BOOT.INI). If you
> want SQL Server to utilize > 4GB memory, you need both settings.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:82A723DF-8EEA-431B-8669-79146E1DCA1D@.microsoft.com...
>
>
|||boot.ini should have something like this:
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws Server 2003,
Enterprise" /fastdetect /pae /3gb
(The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
provide a little more to the apps, i.e. SQL Server.)
To check the amount of physical RAM the OS is seeing you can just check
the Performance tab in task manager.
To turn on AWE memory for SQL Server you use the sp_configure stored
proc (in Query Analyzer for example):
exec sp_configure 'awe enabled', 1
reconfigure
go
Then you have to restart the SQL instance as the AWE setting only takes
affect on server startup. Also, when SQL Server is using AWE memory, it
cannot use dynamic memory management. It *will not swap pages out of
memory *if another app requests memory and the OS doesn't have enough to
satisfy the request (unlike the SQL dynamic memory manager). So you
should specify a "max server memory" amount with sp_configure. For
example, on your 5GB box, if you wanted to allocate 4GB to SQL and the
remaining 1GB to the OS & other apps, you would do this in QA:
exec sp_configure "max server memory", 5120
reconfigure
go
All this is documented in SQL BOL:
http://msdn.microsoft.com/library/de...onfig_3stg.asp
To see how much memory SQL Server is currently consuming you can open
the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff on
AWE & memory management.
HTH
*mike hodgson*
/ mallesons stephen jaques/
blog: http://sqlnerd.blogspot.com
rupart wrote:
[vbcol=seagreen]
>in that case...in a server with 5G of ram
>should i put the /AWE /PAE swith in the same line in the boot.ini?
>For the OS, i can see under system mgmt that 5G is enabled. How abt for sql?
>how do i check it has 5G? Also, is there any significant on it? The
>performance shd be better i suppose
>Thank you
>"Tibor Karaszi" wrote:
>
|||does /3g means the system will allocate 3g for system and the rest for
sql(that is after enabling thru AWE, rite?)?
yeah, good link...thank you
"Mike Hodgson" wrote:
> boot.ini should have something like this:
> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws Server 2003,
> Enterprise" /fastdetect /pae /3gb
> (The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
> provide a little more to the apps, i.e. SQL Server.)
> To check the amount of physical RAM the OS is seeing you can just check
> the Performance tab in task manager.
> To turn on AWE memory for SQL Server you use the sp_configure stored
> proc (in Query Analyzer for example):
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> Then you have to restart the SQL instance as the AWE setting only takes
> affect on server startup. Also, when SQL Server is using AWE memory, it
> cannot use dynamic memory management. It *will not swap pages out of
> memory *if another app requests memory and the OS doesn't have enough to
> satisfy the request (unlike the SQL dynamic memory manager). So you
> should specify a "max server memory" amount with sp_configure. For
> example, on your 5GB box, if you wanted to allocate 4GB to SQL and the
> remaining 1GB to the OS & other apps, you would do this in QA:
> exec sp_configure "max server memory", 5120
> reconfigure
> go
> All this is documented in SQL BOL:
> http://msdn.microsoft.com/library/de...onfig_3stg.asp
> To see how much memory SQL Server is currently consuming you can open
> the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
> Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff on
> AWE & memory management.
> HTH
> --
> *mike hodgson*
> / mallesons stephen jaques/
> blog: http://sqlnerd.blogspot.com
>
> rupart wrote:
>
|||The other way around. 3 GB for the application and 1 GB for the system.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:4944B057-1DC7-4638-BB88-9040FDCC9B9F@.microsoft.com...[vbcol=seagreen]
> does /3g means the system will allocate 3g for system and the rest for
> sql(that is after enabling thru AWE, rite?)?
> yeah, good link...thank you
> "Mike Hodgson" wrote:
|||Oops - slight typo in my "max server memory" statement. To set a max
server memory of 4GB you would run:
exec sp_configure "max server memory", 4096
reconfigure
go
The 5120 figure I included in my previous post would try to set it at
5GB (not 4GB).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Mike Hodgson wrote:
[vbcol=seagreen]
> boot.ini should have something like this:
> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws Server 2003,
> Enterprise" /fastdetect /pae /3gb
> (The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
> provide a little more to the apps, i.e. SQL Server.)
> To check the amount of physical RAM the OS is seeing you can just
> check the Performance tab in task manager.
> To turn on AWE memory for SQL Server you use the sp_configure stored
> proc (in Query Analyzer for example):
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> Then you have to restart the SQL instance as the AWE setting only
> takes affect on server startup. Also, when SQL Server is using AWE
> memory, it cannot use dynamic memory management. It *will not swap
> pages out of memory *if another app requests memory and the OS doesn't
> have enough to satisfy the request (unlike the SQL dynamic memory
> manager). So you should specify a "max server memory" amount with
> sp_configure. For example, on your 5GB box, if you wanted to allocate
> 4GB to SQL and the remaining 1GB to the OS & other apps, you would do
> this in QA:
> exec sp_configure "max server memory", 5120
> reconfigure
> go
> All this is documented in SQL BOL:
> http://msdn.microsoft.com/library/de...nfig_3stg..asp
> To see how much memory SQL Server is currently consuming you can open
> the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
> Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff
> on AWE & memory management.
> HTH
> --
> *mike hodgson*
> / mallesons stephen jaques/
> blog: http://sqlnerd.blogspot.com
>
> rupart wrote:
http://searchsqlserver.techtarget.com/tip/1,289483,sid87_gci1146801,00.htmlPAE allows the OS to use more than 4GB of memory. AWE allows the
application to use more than 4GB.
Andrew J. Kelly SQL MVP
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:7D318157-43B8-49AD-9DF7-F38F6ABEEA03@.microsoft.com...
> guys,
> what is the difference between AWE and PAE?
|||for SQL server, shd i enable PAE or AWE? Can both be enabled at the same time?
"Andrew J. Kelly" wrote:
> PAE allows the OS to use more than 4GB of memory. AWE allows the
> application to use more than 4GB.
> --
> Andrew J. Kelly SQL MVP
>
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:7D318157-43B8-49AD-9DF7-F38F6ABEEA03@.microsoft.com...
>
>
|||AWE is a SQL Server setting (sp_configure) and PAE is an operating system setting (BOOT.INI). If you
want SQL Server to utilize > 4GB memory, you need both settings.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:82A723DF-8EEA-431B-8669-79146E1DCA1D@.microsoft.com...[vbcol=seagreen]
> for SQL server, shd i enable PAE or AWE? Can both be enabled at the same time?
> "Andrew J. Kelly" wrote:
|||in that case...in a server with 5G of ram
should i put the /AWE /PAE swith in the same line in the boot.ini?
For the OS, i can see under system mgmt that 5G is enabled. How abt for sql?
how do i check it has 5G? Also, is there any significant on it? The
performance shd be better i suppose
Thank you
"Tibor Karaszi" wrote:
> AWE is a SQL Server setting (sp_configure) and PAE is an operating system setting (BOOT.INI). If you
> want SQL Server to utilize > 4GB memory, you need both settings.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "rupart" <rupart@.discussions.microsoft.com> wrote in message
> news:82A723DF-8EEA-431B-8669-79146E1DCA1D@.microsoft.com...
>
>
|||boot.ini should have something like this:
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws Server 2003,
Enterprise" /fastdetect /pae /3gb
(The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
provide a little more to the apps, i.e. SQL Server.)
To check the amount of physical RAM the OS is seeing you can just check
the Performance tab in task manager.
To turn on AWE memory for SQL Server you use the sp_configure stored
proc (in Query Analyzer for example):
exec sp_configure 'awe enabled', 1
reconfigure
go
Then you have to restart the SQL instance as the AWE setting only takes
affect on server startup. Also, when SQL Server is using AWE memory, it
cannot use dynamic memory management. It *will not swap pages out of
memory *if another app requests memory and the OS doesn't have enough to
satisfy the request (unlike the SQL dynamic memory manager). So you
should specify a "max server memory" amount with sp_configure. For
example, on your 5GB box, if you wanted to allocate 4GB to SQL and the
remaining 1GB to the OS & other apps, you would do this in QA:
exec sp_configure "max server memory", 5120
reconfigure
go
All this is documented in SQL BOL:
http://msdn.microsoft.com/library/de...onfig_3stg.asp
To see how much memory SQL Server is currently consuming you can open
the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff on
AWE & memory management.
HTH
*mike hodgson*
/ mallesons stephen jaques/
blog: http://sqlnerd.blogspot.com
rupart wrote:
[vbcol=seagreen]
>in that case...in a server with 5G of ram
>should i put the /AWE /PAE swith in the same line in the boot.ini?
>For the OS, i can see under system mgmt that 5G is enabled. How abt for sql?
>how do i check it has 5G? Also, is there any significant on it? The
>performance shd be better i suppose
>Thank you
>"Tibor Karaszi" wrote:
>
|||does /3g means the system will allocate 3g for system and the rest for
sql(that is after enabling thru AWE, rite?)?
yeah, good link...thank you
"Mike Hodgson" wrote:
> boot.ini should have something like this:
> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws Server 2003,
> Enterprise" /fastdetect /pae /3gb
> (The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
> provide a little more to the apps, i.e. SQL Server.)
> To check the amount of physical RAM the OS is seeing you can just check
> the Performance tab in task manager.
> To turn on AWE memory for SQL Server you use the sp_configure stored
> proc (in Query Analyzer for example):
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> Then you have to restart the SQL instance as the AWE setting only takes
> affect on server startup. Also, when SQL Server is using AWE memory, it
> cannot use dynamic memory management. It *will not swap pages out of
> memory *if another app requests memory and the OS doesn't have enough to
> satisfy the request (unlike the SQL dynamic memory manager). So you
> should specify a "max server memory" amount with sp_configure. For
> example, on your 5GB box, if you wanted to allocate 4GB to SQL and the
> remaining 1GB to the OS & other apps, you would do this in QA:
> exec sp_configure "max server memory", 5120
> reconfigure
> go
> All this is documented in SQL BOL:
> http://msdn.microsoft.com/library/de...onfig_3stg.asp
> To see how much memory SQL Server is currently consuming you can open
> the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
> Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff on
> AWE & memory management.
> HTH
> --
> *mike hodgson*
> / mallesons stephen jaques/
> blog: http://sqlnerd.blogspot.com
>
> rupart wrote:
>
|||The other way around. 3 GB for the application and 1 GB for the system.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"rupart" <rupart@.discussions.microsoft.com> wrote in message
news:4944B057-1DC7-4638-BB88-9040FDCC9B9F@.microsoft.com...[vbcol=seagreen]
> does /3g means the system will allocate 3g for system and the rest for
> sql(that is after enabling thru AWE, rite?)?
> yeah, good link...thank you
> "Mike Hodgson" wrote:
|||Oops - slight typo in my "max server memory" statement. To set a max
server memory of 4GB you would run:
exec sp_configure "max server memory", 4096
reconfigure
go
The 5120 figure I included in my previous post would try to set it at
5GB (not 4GB).
*mike hodgson*
blog: http://sqlnerd.blogspot.com
Mike Hodgson wrote:
[vbcol=seagreen]
> boot.ini should have something like this:
> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Windo ws Server 2003,
> Enterprise" /fastdetect /pae /3gb
> (The /3gb switch is not necessary, but for a box with 5gb of RAM it'll
> provide a little more to the apps, i.e. SQL Server.)
> To check the amount of physical RAM the OS is seeing you can just
> check the Performance tab in task manager.
> To turn on AWE memory for SQL Server you use the sp_configure stored
> proc (in Query Analyzer for example):
> exec sp_configure 'awe enabled', 1
> reconfigure
> go
> Then you have to restart the SQL instance as the AWE setting only
> takes affect on server startup. Also, when SQL Server is using AWE
> memory, it cannot use dynamic memory management. It *will not swap
> pages out of memory *if another app requests memory and the OS doesn't
> have enough to satisfy the request (unlike the SQL dynamic memory
> manager). So you should specify a "max server memory" amount with
> sp_configure. For example, on your 5GB box, if you wanted to allocate
> 4GB to SQL and the remaining 1GB to the OS & other apps, you would do
> this in QA:
> exec sp_configure "max server memory", 5120
> reconfigure
> go
> All this is documented in SQL BOL:
> http://msdn.microsoft.com/library/de...nfig_3stg..asp
> To see how much memory SQL Server is currently consuming you can open
> the System Monitor (perfmon.exe) and add the counter: SQLServer:Memory
> Manager | Total Server Memory (KB). SQL BOL has a lot of good stuff
> on AWE & memory management.
> HTH
> --
> *mike hodgson*
> / mallesons stephen jaques/
> blog: http://sqlnerd.blogspot.com
>
> rupart wrote:
Monday, February 13, 2012
Avast Antivirus causing SQL Server 2005 not to start up
I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
developer PC. I installed SQL Server 2005 SP2 last week and installed
Avast Antivirus this week. What I noticed was that after my reboot, I
could not get SQL Server to start. In the Surface Area Configuration,
I was getting error messages in regards to me not having permission to
start the service.
So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
Alas, SQL Server 2005 was starting up again!
I use AVG Antivirus (free of course), and was wondering if anybody
else out there has had similar problems? Is it just Avast?
Thanks.
"tofu.captain" <tofu.captain@.gmail.com> wrote in message
news:1176693441.180857.3870@.w1g2000hsg.googlegroup s.com...
>I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
Generally suggest not running an AV on a SQL Server. At the very least
suggest telling it to not scan the databases.
> Thanks.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Hi
"tofu.captain" wrote:
> I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
> Thanks.
>
As this is a developer PC you probably do want to install an antivirus
program, but as Greg says do not scan the database files as SQL Server will
require exclusive access to these files. I would expect user databases to be
marked as suspect if the scan was occurring during start up, but SQL Server
may still start therefore the error message seems slightly spurious. Have you
checked the SQL Server log and the event log for any additional information?
John
developer PC. I installed SQL Server 2005 SP2 last week and installed
Avast Antivirus this week. What I noticed was that after my reboot, I
could not get SQL Server to start. In the Surface Area Configuration,
I was getting error messages in regards to me not having permission to
start the service.
So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
Alas, SQL Server 2005 was starting up again!
I use AVG Antivirus (free of course), and was wondering if anybody
else out there has had similar problems? Is it just Avast?
Thanks.
"tofu.captain" <tofu.captain@.gmail.com> wrote in message
news:1176693441.180857.3870@.w1g2000hsg.googlegroup s.com...
>I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
Generally suggest not running an AV on a SQL Server. At the very least
suggest telling it to not scan the databases.
> Thanks.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html
|||Hi
"tofu.captain" wrote:
> I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
> Thanks.
>
As this is a developer PC you probably do want to install an antivirus
program, but as Greg says do not scan the database files as SQL Server will
require exclusive access to these files. I would expect user databases to be
marked as suspect if the scan was occurring during start up, but SQL Server
may still start therefore the error message seems slightly spurious. Have you
checked the SQL Server log and the event log for any additional information?
John
Avast Antivirus causing SQL Server 2005 not to start up
I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
developer PC. I installed SQL Server 2005 SP2 last week and installed
Avast Antivirus this week. What I noticed was that after my reboot, I
could not get SQL Server to start. In the Surface Area Configuration,
I was getting error messages in regards to me not having permission to
start the service.
So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
Alas, SQL Server 2005 was starting up again!
I use AVG Antivirus (free of course), and was wondering if anybody
else out there has had similar problems? Is it just Avast?
Thanks."tofu.captain" <tofu.captain@.gmail.com> wrote in message
news:1176693441.180857.3870@.w1g2000hsg.googlegroups.com...
>I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
Generally suggest not running an AV on a SQL Server. At the very least
suggest telling it to not scan the databases.
> Thanks.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi
"tofu.captain" wrote:
> I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
> Thanks.
>
As this is a developer PC you probably do want to install an antivirus
program, but as Greg says do not scan the database files as SQL Server will
require exclusive access to these files. I would expect user databases to be
marked as suspect if the scan was occurring during start up, but SQL Server
may still start therefore the error message seems slightly spurious. Have yo
u
checked the SQL Server log and the event log for any additional information?
John
developer PC. I installed SQL Server 2005 SP2 last week and installed
Avast Antivirus this week. What I noticed was that after my reboot, I
could not get SQL Server to start. In the Surface Area Configuration,
I was getting error messages in regards to me not having permission to
start the service.
So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
Alas, SQL Server 2005 was starting up again!
I use AVG Antivirus (free of course), and was wondering if anybody
else out there has had similar problems? Is it just Avast?
Thanks."tofu.captain" <tofu.captain@.gmail.com> wrote in message
news:1176693441.180857.3870@.w1g2000hsg.googlegroups.com...
>I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
Generally suggest not running an AV on a SQL Server. At the very least
suggest telling it to not scan the databases.
> Thanks.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi
"tofu.captain" wrote:
> I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
> Thanks.
>
As this is a developer PC you probably do want to install an antivirus
program, but as Greg says do not scan the database files as SQL Server will
require exclusive access to these files. I would expect user databases to be
marked as suspect if the scan was occurring during start up, but SQL Server
may still start therefore the error message seems slightly spurious. Have yo
u
checked the SQL Server log and the event log for any additional information?
John
Avast Antivirus causing SQL Server 2005 not to start up
I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
developer PC. I installed SQL Server 2005 SP2 last week and installed
Avast Antivirus this week. What I noticed was that after my reboot, I
could not get SQL Server to start. In the Surface Area Configuration,
I was getting error messages in regards to me not having permission to
start the service.
So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
Alas, SQL Server 2005 was starting up again!
I use AVG Antivirus (free of course), and was wondering if anybody
else out there has had similar problems? Is it just Avast?
Thanks."tofu.captain" <tofu.captain@.gmail.com> wrote in message
news:1176693441.180857.3870@.w1g2000hsg.googlegroups.com...
>I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
Generally suggest not running an AV on a SQL Server. At the very least
suggest telling it to not scan the databases.
> Thanks.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi
"tofu.captain" wrote:
> I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
> Thanks.
>
As this is a developer PC you probably do want to install an antivirus
program, but as Greg says do not scan the database files as SQL Server will
require exclusive access to these files. I would expect user databases to be
marked as suspect if the scan was occurring during start up, but SQL Server
may still start therefore the error message seems slightly spurious. Have you
checked the SQL Server log and the event log for any additional information?
John
developer PC. I installed SQL Server 2005 SP2 last week and installed
Avast Antivirus this week. What I noticed was that after my reboot, I
could not get SQL Server to start. In the Surface Area Configuration,
I was getting error messages in regards to me not having permission to
start the service.
So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
Alas, SQL Server 2005 was starting up again!
I use AVG Antivirus (free of course), and was wondering if anybody
else out there has had similar problems? Is it just Avast?
Thanks."tofu.captain" <tofu.captain@.gmail.com> wrote in message
news:1176693441.180857.3870@.w1g2000hsg.googlegroups.com...
>I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
Generally suggest not running an AV on a SQL Server. At the very least
suggest telling it to not scan the databases.
> Thanks.
>
Greg Moore
SQL Server DBA Consulting Remote and Onsite available!
Email: sql (at) greenms.com http://www.greenms.com/sqlserver.html|||Hi
"tofu.captain" wrote:
> I have SQL Server 2005 and Visual Studio .NET 2005 installed on my
> developer PC. I installed SQL Server 2005 SP2 last week and installed
> Avast Antivirus this week. What I noticed was that after my reboot, I
> could not get SQL Server to start. In the Surface Area Configuration,
> I was getting error messages in regards to me not having permission to
> start the service.
> So I uninstalled Avast Antivirus (Home Edition btw), and rebooted.
> Alas, SQL Server 2005 was starting up again!
> I use AVG Antivirus (free of course), and was wondering if anybody
> else out there has had similar problems? Is it just Avast?
> Thanks.
>
As this is a developer PC you probably do want to install an antivirus
program, but as Greg says do not scan the database files as SQL Server will
require exclusive access to these files. I would expect user databases to be
marked as suspect if the scan was occurring during start up, but SQL Server
may still start therefore the error message seems slightly spurious. Have you
checked the SQL Server log and the event log for any additional information?
John
Sunday, February 12, 2012
Auto-refresh the output of the 'Open Table" action
I checked the options in SQL 2005 Management Studio and it does not appear to be an
available functionality.
Is it possible to have the output of the "Open table" action to refresh the output at a
specified interval?
Thanks.
Probably not as it was never designed for that. There are few reasons to
use that functionality in the first place. The query editior is far more
flexible and does not run the risk of editing data by mistake just from
viewing the data.
Andrew J. Kelly SQL MVP
"Gaetan" <me@.somewhere.com> wrote in message
news:ge2h125kt8381rls43qv4ie3181j1c981r@.4ax.com...
>I checked the options in SQL 2005 Management Studio and it does not appear
>to be an
> available functionality.
> Is it possible to have the output of the "Open table" action to refresh
> the output at a
> specified interval?
> Thanks.
|||I understand the limitations of "Open table". The Query Editor is far more flexible but
unless I missed something, it too does not allow the SQL statements to be auto-rerun at
configurable interval.
On Wed, 15 Mar 2006 19:52:00 -0500, "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote:
>Probably not as it was never designed for that. There are few reasons to
>use that functionality in the first place. The query editior is far more
>flexible and does not run the risk of editing data by mistake just from
>viewing the data.
|||Not as a built in feature but a simple while loop will do it for you. This
will rerun the query every to seconds for 10 loops. Or what ever you need
it to do.
DECLARE @.X INT
SET @.X = 0
WHILE @.x < 10
BEGIN
SELECT *****
WAITFOR DELAY '00:00:10'
END
Andrew J. Kelly SQL MVP
"Gaetan" <me@.somewhere.com> wrote in message
news:6kej12dd7b63n4cq7tr61j26iejd9g7pv9@.4ax.com... [vbcol=seagreen]
>I understand the limitations of "Open table". The Query Editor is far more
>flexible but
> unless I missed something, it too does not allow the SQL statements to be
> auto-rerun at
> configurable interval.
>
> On Wed, 15 Mar 2006 19:52:00 -0500, "Andrew J. Kelly"
> <sqlmvpnooospam@.shadhawk.com> wrote:
available functionality.
Is it possible to have the output of the "Open table" action to refresh the output at a
specified interval?
Thanks.
Probably not as it was never designed for that. There are few reasons to
use that functionality in the first place. The query editior is far more
flexible and does not run the risk of editing data by mistake just from
viewing the data.
Andrew J. Kelly SQL MVP
"Gaetan" <me@.somewhere.com> wrote in message
news:ge2h125kt8381rls43qv4ie3181j1c981r@.4ax.com...
>I checked the options in SQL 2005 Management Studio and it does not appear
>to be an
> available functionality.
> Is it possible to have the output of the "Open table" action to refresh
> the output at a
> specified interval?
> Thanks.
|||I understand the limitations of "Open table". The Query Editor is far more flexible but
unless I missed something, it too does not allow the SQL statements to be auto-rerun at
configurable interval.
On Wed, 15 Mar 2006 19:52:00 -0500, "Andrew J. Kelly" <sqlmvpnooospam@.shadhawk.com> wrote:
>Probably not as it was never designed for that. There are few reasons to
>use that functionality in the first place. The query editior is far more
>flexible and does not run the risk of editing data by mistake just from
>viewing the data.
|||Not as a built in feature but a simple while loop will do it for you. This
will rerun the query every to seconds for 10 loops. Or what ever you need
it to do.
DECLARE @.X INT
SET @.X = 0
WHILE @.x < 10
BEGIN
SELECT *****
WAITFOR DELAY '00:00:10'
END
Andrew J. Kelly SQL MVP
"Gaetan" <me@.somewhere.com> wrote in message
news:6kej12dd7b63n4cq7tr61j26iejd9g7pv9@.4ax.com... [vbcol=seagreen]
>I understand the limitations of "Open table". The Query Editor is far more
>flexible but
> unless I missed something, it too does not allow the SQL statements to be
> auto-rerun at
> configurable interval.
>
> On Wed, 15 Mar 2006 19:52:00 -0500, "Andrew J. Kelly"
> <sqlmvpnooospam@.shadhawk.com> wrote:
Subscribe to:
Posts (Atom)