[SUGGESTION] Upload reports as ZIP file

Hi all,
I have around 200 reports, and it is overkill to upload them to server
file by file. So I suggest, man could pack them to ZIP and upload one
ZIP file, or I am missing something ?
/branoYou can zip the files, upload and unzip. But you still need to upload it to
the Report Server. You can do it more or less automatically with a script.
You can read a suggestion on how to at
http://blogs.spipp.net/kaisa/archive/2005/12/13/1233.aspx .
There are also some references to a scripting tool called "Reporting
Services Scripter", which can be found at
http://www.sqldbatips.com/samples/code/RSScripter/readme.htm
(Haven't tested it myself.)
Kaisa M. Lindahl
"Brano" <2ge@.2NOgeSPAM.us> wrote in message
news:245690956.20060118121838@.ble.com...
> Hi all,
> I have around 200 reports, and it is overkill to upload them to server
> file by file. So I suggest, man could pack them to ZIP and upload one
> ZIP file, or I am missing something ?
> /brano
>|||Hello Kaisa,
Wednesday, January 18, 2006, 1:41:28 PM, you wrote:
> You can zip the files, upload and unzip. But you still need to upload it to
> the Report Server. You can do it more or less automatically with a script.
> You can read a suggestion on how to at
> http://blogs.spipp.net/kaisa/archive/2005/12/13/1233.aspx .
thanks, I understood it.
> There are also some references to a scripting tool called "Reporting
> Services Scripter", which can be found at
> http://www.sqldbatips.com/samples/code/RSScripter/readme.htm
> (Haven't tested it myself.)
you should, it is very powerful app designed exactly for this.
Importing (deploying) is quite slow, but it is faster and more correct
as doing by hand.
Thanks for nice suggestion.
Best regards,
Brano mailto:2ge@.2NOgeSPAM.us

[165]ODBC Error 0 Timeout expired[SQLSTATE HYT00]

sql server 2000 8.00.194
Microsoft Windows 2000 Service Pack 2

I looked into my sqlserver agent log and found the following

ODBC Error 0 Timeout expired[SQLSTATE HYT00]
logon to server local '( failed)' (Job manager)

I have no idea what that means but it did keep out users for a minute or more.
The threads found on this forum almost all point to reccuring situations
mine is a sporadic one time issue.
Is it Ok to conclude it is a network error as I did?

TIA
VinceVincento Harris (wumutek@.yahoo.com) writes:
> sql server 2000 8.00.194

That's an SQL Server with no service pack. I strongly encouarge you to
download and install Service Pack 3.

> I looked into my sqlserver agent log and found the following
> ODBC Error 0 Timeout expired[SQLSTATE HYT00]
> logon to server local '( failed)' (Job manager)
> I have no idea what that means but it did keep out users for a minute or
> more. The threads found on this forum almost all point to reccuring
> situations mine is a sporadic one time issue.
> Is it Ok to conclude it is a network error as I did?

This may be a correct conclusion in the end, but it is not the most likely.

The ODBC error "Timeout expired" means that a query did not start to
return rows with the timeout period, which by default is 30 seconds.
The reason for this could be that the query itself needed longer time
to execute, because of large amounts of data to search and/or poor
indexing. It could also be that the query was blocked by another query,
and that query was long-running. In fact it does not have to be a query
as such that was blocking, but a process holding locks because of
an earlier abandoned query, which was not properly handled.

All this could have been started by some abnormal event like a
network glitch. However, it is much more likely that there was
some inappropriate SQL statement somewhere.

--
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

@@Version still shows Service Pack 1

We just installed the service pack 2 to our server, so I did a select @.@.version but it's still say Service Pack 1, even though the version number is now 3054. Is that a bug in the service pack?

Thanks.

Can you post the entire string returned by SELECT @.@.VERSION? My guess is that you are seeing the Windows OS Service Pack that is also included in the @.@.VERSION call. SQL Server should return SP2.

Thanks,

Sam Lester (MSFT)

|||Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86) Mar 23 2007 16:28:52 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)
|||

Yeah, the SP1 in this case refers to your Windows Version:

Windows NT 5.2 (Build 3790: Service Pack 1)

The Service Pack level apparently isn't listed in the @.@.VERSION as I thought it was. Build 3054 is definitely SP2, but you can also check Add/Remove Programs report or the setup regitry hives to confirm.

Thanks,
Sam Lester (MSFT)

|||
Thanks for your help.

@@Version not updating

Greetings,
I recently installed Service Pack 4 on SQL 2000. The install went
smooth with no errors and a message at the end stating the install
completed successfully. I rebooted the server (Windows Server '03) and
tried to check the @.@.Version global variable but it still lists only
Service Pack 1.
Could it be that SP4 didn't install? Or is it more likely something
else is preventing the @.@.Version from updating?
Thanks in advance,
BenHi Ben
What do you get from
SELECT SERVERPROPERTY('ProductLevel')
HTH
Kalen Delaney, SQL Server MVP
"sullins602" <ben.sullins@.gmail.com> wrote in message
news:1152814872.081466.270730@.s13g2000cwa.googlegroups.com...
> Greetings,
> I recently installed Service Pack 4 on SQL 2000. The install went
> smooth with no errors and a message at the end stating the install
> completed successfully. I rebooted the server (Windows Server '03) and
> tried to check the @.@.Version global variable but it still lists only
> Service Pack 1.
> Could it be that SP4 didn't install? Or is it more likely something
> else is preventing the @.@.Version from updating?
> Thanks in advance,
> Ben
>|||Hi Ben,
Looks like @.@.version does not show the SQL Server service pack number but a
version number. Check for a number like 8.00.2039. Probably the service pack
listed is for the operating system.
Hope this helps,
Ben Nevarez, MCDBA, OCP
Database Administrator
"sullins602" wrote:

> Greetings,
> I recently installed Service Pack 4 on SQL 2000. The install went
> smooth with no errors and a message at the end stating the install
> completed successfully. I rebooted the server (Windows Server '03) and
> tried to check the @.@.Version global variable but it still lists only
> Service Pack 1.
> Could it be that SP4 didn't install? Or is it more likely something
> else is preventing the @.@.Version from updating?
> Thanks in advance,
> Ben
>|||Thats it! I was looking at the service pack for the OS not the
database. Thanks for your help fellas...
-ben

@@Version not updating

Greetings,
I recently installed Service Pack 4 on SQL 2000. The install went
smooth with no errors and a message at the end stating the install
completed successfully. I rebooted the server (Windows Server '03) and
tried to check the @.@.Version global variable but it still lists only
Service Pack 1.
Could it be that SP4 didn't install? Or is it more likely something
else is preventing the @.@.Version from updating?
Thanks in advance,
BenHi Ben
What do you get from
SELECT SERVERPROPERTY('ProductLevel')
--
HTH
Kalen Delaney, SQL Server MVP
"sullins602" <ben.sullins@.gmail.com> wrote in message
news:1152814872.081466.270730@.s13g2000cwa.googlegroups.com...
> Greetings,
> I recently installed Service Pack 4 on SQL 2000. The install went
> smooth with no errors and a message at the end stating the install
> completed successfully. I rebooted the server (Windows Server '03) and
> tried to check the @.@.Version global variable but it still lists only
> Service Pack 1.
> Could it be that SP4 didn't install? Or is it more likely something
> else is preventing the @.@.Version from updating?
> Thanks in advance,
> Ben
>|||Hi Ben,
Looks like @.@.version does not show the SQL Server service pack number but a
version number. Check for a number like 8.00.2039. Probably the service pack
listed is for the operating system.
Hope this helps,
Ben Nevarez, MCDBA, OCP
Database Administrator
"sullins602" wrote:
> Greetings,
> I recently installed Service Pack 4 on SQL 2000. The install went
> smooth with no errors and a message at the end stating the install
> completed successfully. I rebooted the server (Windows Server '03) and
> tried to check the @.@.Version global variable but it still lists only
> Service Pack 1.
> Could it be that SP4 didn't install? Or is it more likely something
> else is preventing the @.@.Version from updating?
> Thanks in advance,
> Ben
>|||Thats it! I was looking at the service pack for the OS not the
database. Thanks for your help fellas...
-ben