Page break & Service Pack !

Can anyone let me know how I check which Service Pack I do have in SQL
Server Reporting Services.
The second problem is in the reporting services I can see all the pages but
when I export in to PDF I can see proper page break, any idea what's the
problem.
ThanksOn Oct 12, 10:01 am, "Rogers" <naiss...@.hotmail.com> wrote:
> Can anyone let me know how I check which Service Pack I do have in SQL
> Server Reporting Services.
> The second problem is in the reporting services I can see all the pages but
> when I export in to PDF I can see proper page break, any idea what's the
> problem.
> Thanks
The first answer is as follows:
SELECT SERVERPROPERTY('productversion') AS SQLServerVersion,
SERVERPROPERTY ('productlevel') AS ServicePackLevel, SERVERPROPERTY
('edition') AS SQLServerEdition
To get version specs check this link.
http://support.microsoft.com/default.aspx?scid=kb;en-us;q321185
For the second question, if I'm understanding you correctly, the
interface has no page breaks by default. it all appears as a single
page. The PDF renderer breaks it up into pages.
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Is that version gave me SQL Server Reporting Services.
"EMartinez" <emartinez.pr1@.gmail.com> wrote in message
news:1192244268.917148.26670@.e9g2000prf.googlegroups.com...
> On Oct 12, 10:01 am, "Rogers" <naiss...@.hotmail.com> wrote:
>> Can anyone let me know how I check which Service Pack I do have in SQL
>> Server Reporting Services.
>> The second problem is in the reporting services I can see all the pages
>> but
>> when I export in to PDF I can see proper page break, any idea what's the
>> problem.
>> Thanks
>
> The first answer is as follows:
> SELECT SERVERPROPERTY('productversion') AS SQLServerVersion,
> SERVERPROPERTY ('productlevel') AS ServicePackLevel, SERVERPROPERTY
> ('edition') AS SQLServerEdition
> To get version specs check this link.
> http://support.microsoft.com/default.aspx?scid=kb;en-us;q321185
> For the second question, if I'm understanding you correctly, the
> interface has no page breaks by default. it all appears as a single
> page. The PDF renderer breaks it up into pages.
> Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||On Oct 15, 8:46 am, "Rogers" <naiss...@.hotmail.com> wrote:
> Is that version gave me SQL Server Reporting Services.
> "EMartinez" <emartinez...@.gmail.com> wrote in message
> news:1192244268.917148.26670@.e9g2000prf.googlegroups.com...
> > On Oct 12, 10:01 am, "Rogers" <naiss...@.hotmail.com> wrote:
> >> Can anyone let me know how I check which Service Pack I do have in SQL
> >> Server Reporting Services.
> >> The second problem is in the reporting services I can see all the pages
> >> but
> >> when I export in to PDF I can see proper page break, any idea what's the
> >> problem.
> >> Thanks
> > The first answer is as follows:
> > SELECT SERVERPROPERTY('productversion') AS SQLServerVersion,
> > SERVERPROPERTY ('productlevel') AS ServicePackLevel, SERVERPROPERTY
> > ('edition') AS SQLServerEdition
> > To get version specs check this link.
> >http://support.microsoft.com/default.aspx?scid=kb;en-us;q321185
> > For the second question, if I'm understanding you correctly, the
> > interface has no page breaks by default. it all appears as a single
> > page. The PDF renderer breaks it up into pages.
> > Hope this helps.
> > Regards,
> > Enrique Martinez
> > Sr. Software Consultant
If I understand you correctly, generally speaking, the service pack
level of SQL Server is the same as for SSRS/Reporting Services that
you are running. Hope this clarifies it further.
Regards,
Enrique Martinez
Sr. Software Consultant

Package designer- feature pack

after installing the Microsoft SQL Server 2000 DTS Designer Com feature pack and then restarting my management studio, I still cannot see or edit my dts packages. I also tried editing them in the integration services consule but no luck there. I see them under the msdb and have no option to edit them.

Has anyone got this utility to work?

Thanks,
David

From Management Studio, connect to the server where you have your .dts packages saved, go to Management->Legacy->Data Transformation Service, when you see the list of dts packages, right click on one and choose Open. It works for me fine.

You can not use Integration Service designer to open or edit your .dts packages, that's expected.

Thanks

wenyang

|||Im guessing that your opening the packages stored on a sql 2000 server and not a 2005. I tried moving them to my 2005 server and opening them, but am not seeing them.

Thanks for the response.|||

Yes, I was connecting to a sql2000 instance from a sql2005 server, and everything worked fine that way. I now also tried in your way, I agree there maybe an issue here connecting to a .dts package saved on a sql2005 server, which I am observing right now. However, here is a work around for you to at least make your scenario work

At your box where Sql2005 is installed

1. Connect to a sql2000 instance first to see that the .dts package openned without a problem (that's what I got).

2. In that legacy designer UI, choose save your .dts package as "Structured Storage File" (instead of saving it to a sql server) to the local box.

3. Then in SqlServer2005 Management Studio, go to Management | Legacy | Data Transformation Service, right click and choose "Open package file" pointing to that .dts file.

That works for me and hope the same for you. If not, please let me know what you get and I'll follow up.

Thanks

Wenyang

|||

thanks much. I just got done going through the same scenario..

Cheers.

pack will NOT schedule......

anyone ever encountered this...
i have a package which will execute fine manually but when i try to schedule it, it fails immediately (within the first second).
i can even right click on the scheduled package and do "generate sql script" and then run that script and again, no problem. it just will NOT schedule.
any ideas?
Package? Are you using Oracle or SQL Server?
|||

Depends on what your package is doing. Are you accessing external files? If so, you need to realize who your logged in user is for the job. When you run them manually, they execute as the runner.

Nick

|||

When you execute the package it is running on your permissions but schedule is running on SQL Server Agent permissions. If your SQL Server Agent is installed with local systems account as most developer installations are the schedule fails because SQL Server Agent does not have to permissions to run the package. try the links below to configure SQL Server Agent permissions. Hope this helps.

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_xp_aa-sz_8sdm.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/tsqlref/ts_xp_aa-sz_4jxo.asp