relationships in Project server2k3-> reporting services?

Ok,
We have setup SQL2005 reporting services with MOSS integration. I have
created a datasource that points at our Project server 2003 SQL
database so that we can start to create project server reports. The
data source works just fine BUT its *doesnt* pick up any relationships
between tables from the Project2k3 SQL database.
This means that when you create a report builder report the first
table you selct becomes the primary and no others are visable :( not
very useful for creating meaningful reports.
Questions:
a) How does SQL2005RS read the relationships between table entities in
a remote DB so that they can be used together within the report
builder?
b) Does anyone have recommendations, URLs, How-tos on setting up
reporting services against Project server 2003?
Tips welcome
Al BlakeI have written many reports against the Project Server 2003 database. I have
found there are not relationships in the Project Server database. You always
have to create your own joins of the data.
Most of the time I will create a query using query analyzer, Then use SRS
to group ,filter and sum the data.
Hope this helps
--
Ray McCoppin
http://www.randsmanagement.com
Project Server reports.
"scubaal" wrote:
> Ok,
> We have setup SQL2005 reporting services with MOSS integration. I have
> created a datasource that points at our Project server 2003 SQL
> database so that we can start to create project server reports. The
> data source works just fine BUT its *doesnt* pick up any relationships
> between tables from the Project2k3 SQL database.
> This means that when you create a report builder report the first
> table you selct becomes the primary and no others are visable :( not
> very useful for creating meaningful reports.
> Questions:
> a) How does SQL2005RS read the relationships between table entities in
> a remote DB so that they can be used together within the report
> builder?
> b) Does anyone have recommendations, URLs, How-tos on setting up
> reporting services against Project server 2003?
> Tips welcome
> Al Blake
>|||Thanks for the feedback. I thought that was the case but wanted be
sure I hadnt missed something.
I am quite comfortable in making the queries through SQL QA until I
get the right result but then I am unclear as to how I get this into
the SQL2005RS environment through MOSS.
Are you saying I should define views within the SQL database and then
use report builder to make a report against that?
OR
is there some way to 'parameterise' the Report Model object when you
create it to use a SQL queiry with join as the basis of its model?
As far as I can see when I create a RB model the ONLY option I have is
the datasource I want to use......there doesnt seem to be any way to
create an RBM from a datasourse using
SELECT * FROM A,B WHERE A.ID=B.ID
or am I missing something again?
Regards

Reinstalling Sql Reporting Services

Hi, I uninstalled Sql reporting services through Add/Remove Programs, now i'm trying to install it back but SQL Setup not allowing me to do this as all the checkboxes to select components to install are disabled. I'v tried both running via Add/Remove programs and directly running SQL setup exe. can u guys direct me to something?

regards
faraz

What SKU are you installing? Express with Advanced Services? Something else?

Thanks,
Sam Lester (MSFT)

|||its Enterprise Edition

reinstalling reporting services

so i uninstalled reporting services and rebooted

now when i run setup it doesnt even ask me for any options to fill out, it just runs for a minute and says done, but it doesn't really install anything (IIS sites, DB, etc...)

i deleted the DBs, the IIS sites, and the files left over. i did everything except delete stuff in the registry

what do i have to do to get it to reinstall from scratch?

i tried using the .ini file and using the command line utility with no luckwelcome to the hell that Reporting Services 2000. read chapter 7 of this...

http://www.awprofessional.com/articles/article.asp?p=357694&seqNum=1&rl=1

and then read the whole thing.

SQL 2005 reporting Services is a lot more agreeable.|||so i uninstalled reporting services and rebooted

now when i run setup it doesnt even ask me for any options to fill out, it just runs for a minute and says done, but it doesn't really install anything (IIS sites, DB, etc...)

i deleted the DBs, the IIS sites, and the files left over. i did everything except delete stuff in the registry

what do i have to do to get it to reinstall from scratch?

i tried using the .ini file and using the command line utility with no luck

Check your Sql server Service pack as well as Windows server service pack.It happened to me also.Reboot and Install it again...|||Check your Sql server Service pack as well as Windows server service pack.It happened to me also.Reboot and Install it again...

using all of the latest service packs, and i rebooted twice with the same results :o|||welcome to the hell that Reporting Services 2000. read chapter 7 of this...

http://www.awprofessional.com/articles/article.asp?p=357694&seqNum=1&rl=1

and then read the whole thing.

SQL 2005 reporting Services is a lot more agreeable.

i did read this chapter, and looked over the whole thing

i also read the entire sql reporting services book from the people at www.sqlreportingservices.net

none of their solutions helped

i think i am going to try an unattended installation to try to force it to use my ini file, after that i'm out of ideas|||Some info for your help...

Renaming a computer causes a corresponding name change for the Web server and SQL Server instance (if it is on the same computer).

In some cases, Reporting Services is not functional after a computer name change. If you are running a Windows 2000 server and the ReportServer Windows service runs as Local System, the ReportServer Windows service no longer starts automatically when you restart the computer. If you are running Windows Server 2003, the service will start, but you cannot connect to the report server database. To restore service after a computer name change, follow these steps:

Run rsconfig at the command line to update the encrypted connection information in the report server database. Use this syntax when running rsconfig (your values may be different).

rsconfig -s<NewServerName> -dreportserver -aSQL -uSA -p<SAPassword>

Reset IIS. To do this at the command line, type iisreset.

In the RSWebApplication.config file, modify the ReportServerURL setting to reflect the new server name.

In the RSReportServer.config file, modify the URLRoot setting to reflect the new server name.

Update the URL property of the program item used to access Report Manager from the Start menu. To do this, point to Start, point to Program Files, point to Microsoft SQL Server, point to Reporting Services, right-click on Report Manager. On the Web Document page, update the URL to the new server name.
Open Report Manager and update any shared data sources or report-specific data sources that contain references to the old computer name.
If you are running Windows 2000 server, perform these additional steps:

Manually start the ReportServer Windows service.

Run rsactivate at the command line. Use this syntax when running rsactivate (note that your actual values may be different if you did not install to the default path).

rsactivate -c"%installdir%\Reporting

Services\ReportServer\RSReportServer.config"

Reset IIS. To do this at the command line, type iisreset.

For a period of time, the report server and Report Manager may continue to be available under the previous name if you are using Windows Internet Naming Service (WINS) on your corporate network. WINS maps an IP address to each computer it services. Once WINS refreshes the IP address for the renamed computer, the old computer name can no longer be used to access a report server or Report Manager.|||i did this as well, the problem is that RSCONFIG does not support Named Instances as per Microsoft's website. plus the config files are envrypted - i dont think you can see server names listed in the config files, i remember checking before i did anything

it has to be reinstalled through the GUI which does support named instances

i solved the problem to my issue once again:

asp.net 2.0 was installed on this machine as well, which caused the registry key RootVer to be set to ASP 2.0. This is why the install package was saying that 1.1 was not installed (even though it was). YOu have to temporarily change the RootVer key to 1.1, install, and then set it back. This allows you to reinstall report server etc...

[\\HKLM\SOFTWARE\Microsoft\ASP.NET\RootVer] = "1.1.4322.573"

Re-install problems

TITLE: Microsoft SQL Server Setup

Setup failed because Service MSSQL$SQLExpress is disabled for the current hardware profile. Services must be set with the current Hardware Profile logon property profile enabled. For more information on how to enable the hardware profile logon property refer to the product documentation.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=SQLSetup90&EvtType=28112

BUTTONS:

OK

Hmm....I'm not sure what to do. I looked at the service and it's set to automatic.

Did you take a look at:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=838712&SiteID=1

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||Thank you Jens

Re-install problems

TITLE: Microsoft SQL Server Setup

Setup failed because Service MSSQL$SQLExpress is disabled for the current hardware profile. Services must be set with the current Hardware Profile logon property profile enabled. For more information on how to enable the hardware profile logon property refer to the product documentation.

For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.3042.00&EvtSrc=setup.rll&EvtID=SQLSetup90&EvtType=28112

BUTTONS:

OK

Hmm....I'm not sure what to do. I looked at the service and it's set to automatic.

Did you take a look at:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=838712&SiteID=1

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||Thank you Jens

Reinstall ODBC Components

I'm getting the following error on my XP machine:
The ODBC resource DLL c:\windows\system32\odbcint.dll is a different version
than the ODBC setup dll c:\windows\system32\odbccp32.dll reinstall the ODBC
components to ensure proper operation.
I've reinstalled SQL 7.0 several times, how do I reinstall the ODBC
components?
Thank youReinstall MDAC. Reinstalling SQL Server 7 won't update MDAC
as XP is on a higher version. You can also check your
current MDAC installation with component checker
You can find the MDAC downloads and component checker at:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Wed, 10 Nov 2004 16:24:01 -0800, "Michelle"
<Michelle@.discussions.microsoft.com> wrote:

>I'm getting the following error on my XP machine:
>The ODBC resource DLL c:\windows\system32\odbcint.dll is a different versio
n
>than the ODBC setup dll c:\windows\system32\odbccp32.dll reinstall the ODBC
>components to ensure proper operation.
>I've reinstalled SQL 7.0 several times, how do I reinstall the ODBC
>components?
>Thank you

Reinstall ODBC Components

I'm getting the following error on my XP machine:
The ODBC resource DLL c:\windows\system32\odbcint.dll is a different version
than the ODBC setup dll c:\windows\system32\odbccp32.dll reinstall the ODBC
components to ensure proper operation.
I've reinstalled SQL 7.0 several times, how do I reinstall the ODBC
components?
Thank you
Reinstall MDAC. Reinstalling SQL Server 7 won't update MDAC
as XP is on a higher version. You can also check your
current MDAC installation with component checker
You can find the MDAC downloads and component checker at:
http://msdn.microsoft.com/data/mdac/default.aspx
-Sue
On Wed, 10 Nov 2004 16:24:01 -0800, "Michelle"
<Michelle@.discussions.microsoft.com> wrote:

>I'm getting the following error on my XP machine:
>The ODBC resource DLL c:\windows\system32\odbcint.dll is a different version
>than the ODBC setup dll c:\windows\system32\odbccp32.dll reinstall the ODBC
>components to ensure proper operation.
>I've reinstalled SQL 7.0 several times, how do I reinstall the ODBC
>components?
>Thank you

reinitialization using option to bring back subsriber changes first

I have a merge replication setup. for simplicities sake lets say the
publication has 4 articles(tables). The publishing database has 6
articles(tables). All 6 tables exist both at the publisher and subscriber
from previous repl setups. I make the publcation with the 4 articles...
create the new subscription and initialize it... including schema. Then a
few days later I realize I need to add those other 2 tables to this
publication. Currently the 2 tables on the subscriber end have data in them
and the one on the publishers end has no data. I wanted to add the 2 new
articles but bring back the subscriber data into the emtpy publisher's
table. I did not even know if I could add articles to an existing merge
publication without first dropping subscriptions so I figured I would just
try and EM would tell me if I couldn't. So, it did let me add the articles.
I created a new snapshot containing the new articles and performed a
reinitialize choosing to 'upload the changes at the subscriber before
reinitializing'... expecting the data in the 2 new tables to come back. The
data did not come back. I had empty tables on both ends after the
reinitialization took place. I'm sure that was supposed to happen, I just
didn't know it.
So what I need is to fully understand what data can actually come back from
the subsciber using this option upon a reinitialization? requirements?
('upload the changes at the subscriber before reinitializing')
1) I believe what I had done did not work because those 2 new articles were
NOT a part of the original snapshot and therefore changes to them were not
being tracked... is that correct?
2) the only data that could be brought back from subscriber upon
reinitialization using the 'upload the changes at the subscriber before
reinitializing' option are changes to articles that were a part of the
snapshot that that subscriber was last initialized with? TRUE/FASLE?
3) continuing from 2)... and the purpose of this option is just to get data
from a subscriber that may have 'expired' do to a loss of connectivity to
the publisher for an extended period of time? TRUE/FALSE?
any info is greatly appreciated... thanks.
You are pretty much correct. The "Upload changes first..." option is for
uploading any changes at the Subscriber since the last synchronization.
When you choose to reinitialize the merge agent will first upload changes
since the last synch, then it will start applying the snapshot again. This
time since you've added that article to the publication (you should have to
make a new snapshot) the table at the subscriber side will be overwritten
with what is in the table at the publisher. When the article(table) is
added to the publication you also tell it what to do in the case of
reinitializing (drop, truncate, etc...).
If you are familiar with scripting you could use the sp_addscriptexec stored
procedure to make a script to be propagated to the subscriber in order to
upload the data that exists there to the publisher table. These scripts are
run before anything else I believe when a synch is performed. If you are
using sp_addmergearticle to add the article to the publisher there is a
parameter @.creation_script that you might be able to use to upload the data.
I haven't done this but maybe it gives you a few ideas.
hope it helps,
nate
"djc" <noone@.nowhere.com> wrote in message
news:eIskd73XEHA.1144@.TK2MSFTNGP10.phx.gbl...
> I have a merge replication setup. for simplicities sake lets say the
> publication has 4 articles(tables). The publishing database has 6
> articles(tables). All 6 tables exist both at the publisher and subscriber
> from previous repl setups. I make the publcation with the 4 articles...
> create the new subscription and initialize it... including schema. Then a
> few days later I realize I need to add those other 2 tables to this
> publication. Currently the 2 tables on the subscriber end have data in
them
> and the one on the publishers end has no data. I wanted to add the 2 new
> articles but bring back the subscriber data into the emtpy publisher's
> table. I did not even know if I could add articles to an existing merge
> publication without first dropping subscriptions so I figured I would just
> try and EM would tell me if I couldn't. So, it did let me add the
articles.
> I created a new snapshot containing the new articles and performed a
> reinitialize choosing to 'upload the changes at the subscriber before
> reinitializing'... expecting the data in the 2 new tables to come back.
The
> data did not come back. I had empty tables on both ends after the
> reinitialization took place. I'm sure that was supposed to happen, I just
> didn't know it.
> So what I need is to fully understand what data can actually come back
from
> the subsciber using this option upon a reinitialization? requirements?
> ('upload the changes at the subscriber before reinitializing')
> 1) I believe what I had done did not work because those 2 new articles
were
> NOT a part of the original snapshot and therefore changes to them were not
> being tracked... is that correct?
> 2) the only data that could be brought back from subscriber upon
> reinitialization using the 'upload the changes at the subscriber before
> reinitializing' option are changes to articles that were a part of the
> snapshot that that subscriber was last initialized with? TRUE/FASLE?
> 3) continuing from 2)... and the purpose of this option is just to get
data
> from a subscriber that may have 'expired' do to a loss of connectivity to
> the publisher for an extended period of time? TRUE/FALSE?
> any info is greatly appreciated... thanks.
>
|||yes, it does help. Thank you.
"nate axtell" <naxtell at progeny dot net> wrote in message
news:OVsFx0CYEHA.1684@.tk2msftngp13.phx.gbl...
> You are pretty much correct. The "Upload changes first..." option is for
> uploading any changes at the Subscriber since the last synchronization.
> When you choose to reinitialize the merge agent will first upload changes
> since the last synch, then it will start applying the snapshot again.
This
> time since you've added that article to the publication (you should have
to
> make a new snapshot) the table at the subscriber side will be overwritten
> with what is in the table at the publisher. When the article(table) is
> added to the publication you also tell it what to do in the case of
> reinitializing (drop, truncate, etc...).
> If you are familiar with scripting you could use the sp_addscriptexec
stored
> procedure to make a script to be propagated to the subscriber in order to
> upload the data that exists there to the publisher table. These scripts
are
> run before anything else I believe when a synch is performed. If you are
> using sp_addmergearticle to add the article to the publisher there is a
> parameter @.creation_script that you might be able to use to upload the
data.[vbcol=seagreen]
> I haven't done this but maybe it gives you a few ideas.
> hope it helps,
> nate
> "djc" <noone@.nowhere.com> wrote in message
> news:eIskd73XEHA.1144@.TK2MSFTNGP10.phx.gbl...
subscriber[vbcol=seagreen]
a[vbcol=seagreen]
> them
just[vbcol=seagreen]
> articles.
> The
just[vbcol=seagreen]
> from
> were
not[vbcol=seagreen]
> data
to
>

Reindexing log shipped database

Hallo
I need to setup log shipping on a DB and to create a job that would reindex
that same DB.
If I use a maintenance plan to reindex a DB that is 30 GB in size, it takes
more than 1 hour and during that time the DB is not accessible for users.
This is NOT OK so I'm planning to use a script that would use dbcc
indexdefrag.
I don't know how that would effect transaction log growth. I suspect that
log would grow very much in full-mode or in bulk-logged mode.
But that means that after i set up log shipping on that database, first log
backup after reindexation will be huge and it will take a lot of time to
transfer it over network to secondary server. During that time SQL would
probably not be accessible or time-outs would accour.
Anyone has any advice on this? Or is there any other way to reindex a
log-shipped database?
thanks
Tomyou want to Defrag the "Source" Database or the "Destination" ?
the Destination is a Standby so, essentially, read only. I dont think you
want to be defragging it.
Greg Jackson
PDX, Oregon|||I want to defrag source database. Fregmentation of destination base is not
so important to me.
Tom
"pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
news:%23a$pMckCFHA.1432@.tk2msftngp13.phx.gbl...
> you want to Defrag the "Source" Database or the "Destination" ?
>
> the Destination is a Standby so, essentially, read only. I dont think you
> want to be defragging it.
>
>
> Greg Jackson
> PDX, Oregon
>|||you can use IndexDefrag.
Yes the logging can be fairly extensive and it's a pain to ship the log
activity for index defrags. Defrag indexes regularly so they dont get
massively fragmented. Also monitor fill factor settings etc to reduce
fragmentation.
The database should be available...if not, what is causing it to be blocked
?
your other options are to Reseed the standby server with a full backup after
your defrag jobs.
GAJ|||You should read the whitepaper on fragmentation as it goes into details of
logging. It will also help you determine whether your query workload will
benefit from removing fragmentation regularly.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx
Regards
--
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
news:OVrIHSuCFHA.2676@.TK2MSFTNGP12.phx.gbl...
> you can use IndexDefrag.
> Yes the logging can be fairly extensive and it's a pain to ship the log
> activity for index defrags. Defrag indexes regularly so they dont get
> massively fragmented. Also monitor fill factor settings etc to reduce
> fragmentation.
> The database should be available...if not, what is causing it to be
blocked
> ?
> your other options are to Reseed the standby server with a full backup
after
> your defrag jobs.
>
> GAJ
>

Reindexing log shipped database

Hallo
I need to setup log shipping on a DB and to create a job that would reindex
that same DB.
If I use a maintenance plan to reindex a DB that is 30 GB in size, it takes
more than 1 hour and during that time the DB is not accessible for users.
This is NOT OK so I'm planning to use a script that would use dbcc
indexdefrag.
I don't know how that would effect transaction log growth. I suspect that
log would grow very much in full-mode or in bulk-logged mode.
But that means that after i set up log shipping on that database, first log
backup after reindexation will be huge and it will take a lot of time to
transfer it over network to secondary server. During that time SQL would
probably not be accessible or time-outs would accour.
Anyone has any advice on this? Or is there any other way to reindex a
log-shipped database?
thanks
Tom
you want to Defrag the "Source" Database or the "Destination" ?
the Destination is a Standby so, essentially, read only. I dont think you
want to be defragging it.
Greg Jackson
PDX, Oregon
|||I want to defrag source database. Fregmentation of destination base is not
so important to me.
Tom
"pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
news:%23a$pMckCFHA.1432@.tk2msftngp13.phx.gbl...
> you want to Defrag the "Source" Database or the "Destination" ?
>
> the Destination is a Standby so, essentially, read only. I dont think you
> want to be defragging it.
>
>
> Greg Jackson
> PDX, Oregon
>
|||you can use IndexDefrag.
Yes the logging can be fairly extensive and it's a pain to ship the log
activity for index defrags. Defrag indexes regularly so they dont get
massively fragmented. Also monitor fill factor settings etc to reduce
fragmentation.
The database should be available...if not, what is causing it to be blocked
?
your other options are to Reseed the standby server with a full backup after
your defrag jobs.
GAJ
|||You should read the whitepaper on fragmentation as it goes into details of
logging. It will also help you determine whether your query workload will
benefit from removing fragmentation regularly.
http://www.microsoft.com/technet/pro.../ss2kidbp.mspx
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
news:OVrIHSuCFHA.2676@.TK2MSFTNGP12.phx.gbl...
> you can use IndexDefrag.
> Yes the logging can be fairly extensive and it's a pain to ship the log
> activity for index defrags. Defrag indexes regularly so they dont get
> massively fragmented. Also monitor fill factor settings etc to reduce
> fragmentation.
> The database should be available...if not, what is causing it to be
blocked
> ?
> your other options are to Reseed the standby server with a full backup
after
> your defrag jobs.
>
> GAJ
>

Reindexing log shipped database

Hallo
I need to setup log shipping on a DB and to create a job that would reindex
that same DB.
If I use a maintenance plan to reindex a DB that is 30 GB in size, it takes
more than 1 hour and during that time the DB is not accessible for users.
This is NOT OK so I'm planning to use a script that would use dbcc
indexdefrag.
I don't know how that would effect transaction log growth. I suspect that
log would grow very much in full-mode or in bulk-logged mode.
But that means that after i set up log shipping on that database, first log
backup after reindexation will be huge and it will take a lot of time to
transfer it over network to secondary server. During that time SQL would
probably not be accessible or time-outs would accour.
Anyone has any advice on this? Or is there any other way to reindex a
log-shipped database?
thanks
Tomyou want to Defrag the "Source" Database or the "Destination" ?
the Destination is a Standby so, essentially, read only. I dont think you
want to be defragging it.
Greg Jackson
PDX, Oregon|||I want to defrag source database. Fregmentation of destination base is not
so important to me.
Tom
"pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
news:%23a$pMckCFHA.1432@.tk2msftngp13.phx.gbl...
> you want to Defrag the "Source" Database or the "Destination" ?
>
> the Destination is a Standby so, essentially, read only. I dont think you
> want to be defragging it.
>
>
> Greg Jackson
> PDX, Oregon
>|||you can use IndexDefrag.
Yes the logging can be fairly extensive and it's a pain to ship the log
activity for index defrags. Defrag indexes regularly so they dont get
massively fragmented. Also monitor fill factor settings etc to reduce
fragmentation.
The database should be available...if not, what is causing it to be blocked
?
your other options are to Reseed the standby server with a full backup after
your defrag jobs.
GAJ|||You should read the whitepaper on fragmentation as it goes into details of
logging. It will also help you determine whether your query workload will
benefit from removing fragmentation regularly.
http://www.microsoft.com/technet/pr...n/ss2kidbp.mspx
Regards
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"pdxJaxon" <GregoryAJackson@.Hotmail.com> wrote in message
news:OVrIHSuCFHA.2676@.TK2MSFTNGP12.phx.gbl...
> you can use IndexDefrag.
> Yes the logging can be fairly extensive and it's a pain to ship the log
> activity for index defrags. Defrag indexes regularly so they dont get
> massively fragmented. Also monitor fill factor settings etc to reduce
> fragmentation.
> The database should be available...if not, what is causing it to be
blocked
> ?
> your other options are to Reseed the standby server with a full backup
after
> your defrag jobs.
>
> GAJ
>

Reindexing and Transaction Logs

Hi All,

Just after some feedback on a scenario where we have full logging setup on one of the databases, and the transaction logs are backed up every 60min. At 0000-0100 the log jumps from being a few thousand k up to over 1.7gb.
I did some profiling for this time, and it appears that this jump is related to the reindexing of the indexes on the database.

Is this normal for the log file to jump in size so much? Or is this an indication of some other issue (potentially with the indexes)?

Is there any way that the reindexing can be excluded from the log files or is this a necessity?

Thanks in advance for your help.

Cheers
TroyIt is quite normal for re-indexing to fill up a transaction log. Especially if you use dbcc indexdefrag.|||So I presume there is no 2 ways around this really then? Massive jump in size, which makes for some interesting issues in terms of planning for space *sigh*...|||Your log may stay smaller with database recovery model set to SIMPLE|||haha thanks for that - umm but then I loose my logging...sorta defeats the point of backing up the logs :P
But yeah I hear what you are all saying - suppose I was just after a solution which would allow me to turn off the logging for the index rebuilds and leave it on for all the remainder of the normal i/u/d's in the database...

Thanks all, have a good Christmas/Break/etc...

Regular Backup co-exist with log-shipping (or SQL mirroring)

Suppose I have a 3rd party SQL backup software to backup my databases, can I also setup a stand-by server for log shipping?

I'm not sure if this is possible? If not, is SQL mirroring a choice instead of log shipping?

Thanks a lot!

The only restriction is that only one thread of log backups can exist.

So, if your 3rd-party backup software is also doing log backups, log shipping will not work.

Alternatively, you can do full backups with your 3rd-party software and log shipping will work just fine.

Mirroring has no such restrictions.

Regular Backup co-exist with log-shipping (or SQL mirroring)

Suppose I have a 3rd party SQL backup software to backup my databases, can I also setup a stand-by server for log shipping?

I'm not sure if this is possible? If not, is SQL mirroring a choice instead of log shipping?

Thanks a lot!

The only restriction is that only one thread of log backups can exist.

So, if your 3rd-party backup software is also doing log backups, log shipping will not work.

Alternatively, you can do full backups with your 3rd-party software and log shipping will work just fine.

Mirroring has no such restrictions.

Register an Instance Server

Hello Experts,
I Setup in a machine which is in our network, an SQL
server Instance, then I'm trying to register this server
(from Enterprise Manager) through my machine (it is on
the network), but never connects, what do I do wrong?
Thanks In advance!Have you verified the connection info? The login and pw?
Sincerely,
Invotion Engineering Team
Advanced Microsoft Hosting Solutions
http://www.Invotion.com
>--Original Message--
>Hello Experts,
>I Setup in a machine which is in our network, an SQL
>server Instance, then I'm trying to register this server
>(from Enterprise Manager) through my machine (it is on
>the network), but never connects, what do I do wrong?
>Thanks In advance!
>.
>|||Hello Invotion, yes i did.
>--Original Message--
>Have you verified the connection info? The login and pw?
>Sincerely,
>Invotion Engineering Team
>Advanced Microsoft Hosting Solutions
>http://www.Invotion.com
>>--Original Message--
>>Hello Experts,
>>I Setup in a machine which is in our network, an SQL
>>server Instance, then I'm trying to register this
server
>>(from Enterprise Manager) through my machine (it is on
>>the network), but never connects, what do I do wrong?
>>Thanks In advance!
>>.
>.
>