Hi.
I found this misleading issue and thought I would share it.
We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
fillfactor of 90%. After the plan ran, the database grew by about 70% and
the fill factor was actually 10%.
We found the following in the maint plan:
'Change free space per page percentage to:' We entered 10%.
In hindsight, it meant FILLFACTOR and should have been 90%.
Do you also find this misleading?
The documentation (BOL) reads:
Change free space per page percentage to
Drop the indexes on the tables in the database and re-create them with a
new, automatically calculated fill factor, thereby reserving the specified
amount of free space on the index pages. The higher the percentage, the more
free space is reserved on the index pages, and the larger the index grows.
Valid values are from 0 through 100.
It says the HIGHER the percentage, the more free space is reserved. This
should read LOWER?
Is this a 'bug' in the documentation?
Could someone please pass this onto the Microsoft guys. Maybe they know
about this already.
Thanks!
WayneWayne
I agree that it is a little bit confusing
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
rebuild indexes is logged operation and needs a free space to rebuild all
indexes
Kalen Delaney said
"The first definition
is correct; fillfactor specifies how full each page should be. 30 means 30%
full, 100 means 100% full. The only special case is 0, which means the leaf
level is full, but there is room for one or two rows per page in the upper
levels of the index tree.
I will report this discrepancy in the Books Online definitions. "
http://groups.google.com/group/microsoft.public.sqlserver.programming/browse_thread/thread/eda35e4b5bedab51/535a1ef3d33f1d88?lnk=st&q=&rnum=3&hl=en#535a1ef3d33f1d88
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:D30307D8-C6C6-4196-AB44-76E2F7958714@.microsoft.com...
> Hi.
> I found this misleading issue and thought I would share it.
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
> We found the following in the maint plan:
> 'Change free space per page percentage to:' We entered 10%.
> In hindsight, it meant FILLFACTOR and should have been 90%.
> Do you also find this misleading?
> The documentation (BOL) reads:
>
> Change free space per page percentage to
> Drop the indexes on the tables in the database and re-create them with a
> new, automatically calculated fill factor, thereby reserving the specified
> amount of free space on the index pages. The higher the percentage, the
> more
> free space is reserved on the index pages, and the larger the index grows.
> Valid values are from 0 through 100.
>
> It says the HIGHER the percentage, the more free space is reserved. This
> should read LOWER?
>
> Is this a 'bug' in the documentation?
>
> Could someone please pass this onto the Microsoft guys. Maybe they know
> about this already.
> Thanks!
> Wayne
>|||"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:D30307D8-C6C6-4196-AB44-76E2F7958714@.microsoft.com...
> Hi.
> I found this misleading issue and thought I would share it.
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
> We found the following in the maint plan:
> 'Change free space per page percentage to:' We entered 10%.
> In hindsight, it meant FILLFACTOR and should have been 90%.
> Do you also find this misleading?
> The documentation (BOL) reads:
>
> Change free space per page percentage to
> Drop the indexes on the tables in the database and re-create them with a
> new, automatically calculated fill factor, thereby reserving the specified
> amount of free space on the index pages. The higher the percentage, the
> more
> free space is reserved on the index pages, and the larger the index grows.
> Valid values are from 0 through 100.
>
> It says the HIGHER the percentage, the more free space is reserved. This
> should read LOWER?
>
> Is this a 'bug' in the documentation?
>
> Could someone please pass this onto the Microsoft guys. Maybe they know
> about this already.
>
Anyone can submit doc bugs. The feedback link at the bottom of the BOL
topics will generate an email that automatically creates a doc bug.
David
Showing posts with label box. Show all posts
Showing posts with label box. Show all posts
Thursday, March 29, 2012
Description for fill factor on index rebuild maint plan misleading
Hi.
I found this misleading issue and thought I would share it.
We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
fillfactor of 90%. After the plan ran, the database grew by about 70% and
the fill factor was actually 10%.
We found the following in the maint plan:
'Change free space per page percentage to:' We entered 10%.
In hindsight, it meant FILLFACTOR and should have been 90%.
Do you also find this misleading?
The documentation (BOL) reads:
Change free space per page percentage to
Drop the indexes on the tables in the database and re-create them with a
new, automatically calculated fill factor, thereby reserving the specified
amount of free space on the index pages. The higher the percentage, the more
free space is reserved on the index pages, and the larger the index grows.
Valid values are from 0 through 100.
It says the HIGHER the percentage, the more free space is reserved. This
should read LOWER?
Is this a 'bug' in the documentation?
Could someone please pass this onto the Microsoft guys. Maybe they know
about this already.
Thanks!
WayneWayne
I agree that it is a little bit confusing
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
rebuild indexes is logged operation and needs a free space to rebuild all
indexes
Kalen Delaney said
"The first definition
is correct; fillfactor specifies how full each page should be. 30 means 30%
full, 100 means 100% full. The only special case is 0, which means the leaf
level is full, but there is room for one or two rows per page in the upper
levels of the index tree.
I will report this discrepancy in the Books Online definitions. "
http://groups.google.com/group/micr...33f1d88
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:D30307D8-C6C6-4196-AB44-76E2F7958714@.microsoft.com...
> Hi.
> I found this misleading issue and thought I would share it.
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
> We found the following in the maint plan:
> 'Change free space per page percentage to:' We entered 10%.
> In hindsight, it meant FILLFACTOR and should have been 90%.
> Do you also find this misleading?
> The documentation (BOL) reads:
>
> Change free space per page percentage to
> Drop the indexes on the tables in the database and re-create them with a
> new, automatically calculated fill factor, thereby reserving the specified
> amount of free space on the index pages. The higher the percentage, the
> more
> free space is reserved on the index pages, and the larger the index grows.
> Valid values are from 0 through 100.
>
> It says the HIGHER the percentage, the more free space is reserved. This
> should read LOWER?
>
> Is this a 'bug' in the documentation?
>
> Could someone please pass this onto the Microsoft guys. Maybe they know
> about this already.
> Thanks!
> Wayne
>|||"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:D30307D8-C6C6-4196-AB44-76E2F7958714@.microsoft.com...
> Hi.
> I found this misleading issue and thought I would share it.
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
> We found the following in the maint plan:
> 'Change free space per page percentage to:' We entered 10%.
> In hindsight, it meant FILLFACTOR and should have been 90%.
> Do you also find this misleading?
> The documentation (BOL) reads:
>
> Change free space per page percentage to
> Drop the indexes on the tables in the database and re-create them with a
> new, automatically calculated fill factor, thereby reserving the specified
> amount of free space on the index pages. The higher the percentage, the
> more
> free space is reserved on the index pages, and the larger the index grows.
> Valid values are from 0 through 100.
>
> It says the HIGHER the percentage, the more free space is reserved. This
> should read LOWER?
>
> Is this a 'bug' in the documentation?
>
> Could someone please pass this onto the Microsoft guys. Maybe they know
> about this already.
>
Anyone can submit doc bugs. The feedback link at the bottom of the BOL
topics will generate an email that automatically creates a doc bug.
David
I found this misleading issue and thought I would share it.
We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
fillfactor of 90%. After the plan ran, the database grew by about 70% and
the fill factor was actually 10%.
We found the following in the maint plan:
'Change free space per page percentage to:' We entered 10%.
In hindsight, it meant FILLFACTOR and should have been 90%.
Do you also find this misleading?
The documentation (BOL) reads:
Change free space per page percentage to
Drop the indexes on the tables in the database and re-create them with a
new, automatically calculated fill factor, thereby reserving the specified
amount of free space on the index pages. The higher the percentage, the more
free space is reserved on the index pages, and the larger the index grows.
Valid values are from 0 through 100.
It says the HIGHER the percentage, the more free space is reserved. This
should read LOWER?
Is this a 'bug' in the documentation?
Could someone please pass this onto the Microsoft guys. Maybe they know
about this already.
Thanks!
WayneWayne
I agree that it is a little bit confusing
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
rebuild indexes is logged operation and needs a free space to rebuild all
indexes
Kalen Delaney said
"The first definition
is correct; fillfactor specifies how full each page should be. 30 means 30%
full, 100 means 100% full. The only special case is 0, which means the leaf
level is full, but there is room for one or two rows per page in the upper
levels of the index tree.
I will report this discrepancy in the Books Online definitions. "
http://groups.google.com/group/micr...33f1d88
"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:D30307D8-C6C6-4196-AB44-76E2F7958714@.microsoft.com...
> Hi.
> I found this misleading issue and thought I would share it.
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
> We found the following in the maint plan:
> 'Change free space per page percentage to:' We entered 10%.
> In hindsight, it meant FILLFACTOR and should have been 90%.
> Do you also find this misleading?
> The documentation (BOL) reads:
>
> Change free space per page percentage to
> Drop the indexes on the tables in the database and re-create them with a
> new, automatically calculated fill factor, thereby reserving the specified
> amount of free space on the index pages. The higher the percentage, the
> more
> free space is reserved on the index pages, and the larger the index grows.
> Valid values are from 0 through 100.
>
> It says the HIGHER the percentage, the more free space is reserved. This
> should read LOWER?
>
> Is this a 'bug' in the documentation?
>
> Could someone please pass this onto the Microsoft guys. Maybe they know
> about this already.
> Thanks!
> Wayne
>|||"Wayne" <Wayne@.discussions.microsoft.com> wrote in message
news:D30307D8-C6C6-4196-AB44-76E2F7958714@.microsoft.com...
> Hi.
> I found this misleading issue and thought I would share it.
> We set up a maint plan on a SQL2005 RTM box to rebuild our indexes with a
> fillfactor of 90%. After the plan ran, the database grew by about 70% and
> the fill factor was actually 10%.
> We found the following in the maint plan:
> 'Change free space per page percentage to:' We entered 10%.
> In hindsight, it meant FILLFACTOR and should have been 90%.
> Do you also find this misleading?
> The documentation (BOL) reads:
>
> Change free space per page percentage to
> Drop the indexes on the tables in the database and re-create them with a
> new, automatically calculated fill factor, thereby reserving the specified
> amount of free space on the index pages. The higher the percentage, the
> more
> free space is reserved on the index pages, and the larger the index grows.
> Valid values are from 0 through 100.
>
> It says the HIGHER the percentage, the more free space is reserved. This
> should read LOWER?
>
> Is this a 'bug' in the documentation?
>
> Could someone please pass this onto the Microsoft guys. Maybe they know
> about this already.
>
Anyone can submit doc bugs. The feedback link at the bottom of the BOL
topics will generate an email that automatically creates a doc bug.
David
Sunday, March 25, 2012
Deployment Version Problem
We are trying to deploy a report server project from an XP Dev box to a
Server2003 production environment.
Both computers are running SQL Server 2005 with SP1 installed.
We have tried to deploy by (1) a deploy over the network and (2) a database
backup of the ReportServer database and then a restore to the Server 2003
system.
Both methods give us exactly the same error...
The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'Unknown'. The expected
version is 'C.0.8.43'. To continue, update the version of the report server
database and verify access rights.
Why are we getting this error?
Regards,
GaryHi Gary,
Thank you for your posting!
Based on my research and experience, I think you need to reinstall the SP1
on the Server 2003 box.
Please let me know if you get any error message when you reinstall the SP1.
You could send the setup error log to me if you get any error. By default,
the error log file folder is C:\WINDOWS\Hotfix
Please let me know the result. Thank you!
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.|||Hi Gary,
How is everything going? Please feel free to let me know if you need any
assistance.
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.|||Wei,
It turned out that [apparently] the person who installed sp1 was not a
"member of the SQL Server Administrators Group" and when we followed the
recommeded fix in configuration manager the problem went away.
A mystery that remains for me is that I can't find a "SQL Server
Administrators Group". Do you know exactly what that is? Is it a user with
sysadmin privlidges?
Gary
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:t1rUdcOoGHA.2024@.TK2MSFTNGXA01.phx.gbl...
> Hi Gary,
> How is everything going? Please feel free to let me know if you need any
> assistance.
> 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.
>|||Hi Gary,
Thank you for the update and glad to hear the issue has been resolved.
I think the SQL Server Administrators Group means the SQL Server sysadmin
group. Members of the sysadmin fixed server role can perform any activity
in the server. By default, all members of the Windows
BUILTIN\Administrators group, the local administrator's group, are members
of the sysadmin fixed server role.
If you have any questions or concern, please feel free to let me know.
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.
Server2003 production environment.
Both computers are running SQL Server 2005 with SP1 installed.
We have tried to deploy by (1) a deploy over the network and (2) a database
backup of the ReportServer database and then a restore to the Server 2003
system.
Both methods give us exactly the same error...
The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'Unknown'. The expected
version is 'C.0.8.43'. To continue, update the version of the report server
database and verify access rights.
Why are we getting this error?
Regards,
GaryHi Gary,
Thank you for your posting!
Based on my research and experience, I think you need to reinstall the SP1
on the Server 2003 box.
Please let me know if you get any error message when you reinstall the SP1.
You could send the setup error log to me if you get any error. By default,
the error log file folder is C:\WINDOWS\Hotfix
Please let me know the result. Thank you!
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.|||Hi Gary,
How is everything going? Please feel free to let me know if you need any
assistance.
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.|||Wei,
It turned out that [apparently] the person who installed sp1 was not a
"member of the SQL Server Administrators Group" and when we followed the
recommeded fix in configuration manager the problem went away.
A mystery that remains for me is that I can't find a "SQL Server
Administrators Group". Do you know exactly what that is? Is it a user with
sysadmin privlidges?
Gary
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:t1rUdcOoGHA.2024@.TK2MSFTNGXA01.phx.gbl...
> Hi Gary,
> How is everything going? Please feel free to let me know if you need any
> assistance.
> 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.
>|||Hi Gary,
Thank you for the update and glad to hear the issue has been resolved.
I think the SQL Server Administrators Group means the SQL Server sysadmin
group. Members of the sysadmin fixed server role can perform any activity
in the server. By default, all members of the Windows
BUILTIN\Administrators group, the local administrator's group, are members
of the sysadmin fixed server role.
If you have any questions or concern, please feel free to let me know.
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.
Wednesday, March 21, 2012
Deployment error: Expected C.0.8.43
We are trying to deploy a report server project from an XP Dev box to a Server2003 production environment.
Both computers are running SQL Server 2005 with SP1 installed.
We have tried to deploy by (1) a deploy over the network and (2) a database backup of the ReportServer database and then a restore to the Server 2003 system.
Both methods give us exactly the same error...
The version of the report server database is either in a format that is not valid, or it cannot be read. The found version is 'Unknown'. The expected version is 'C.0.8.43'. To continue, update the version of the report server database and verify access rights.
Why are we getting this error?
Regards,
Gary
Reporting Services data is encrypted. Did you backup and restore the symetric key from the old to the new system ? Otherwiese the information from the report database like report definitions can′t be read.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Check out this link. It does not directly apply to your problem, but it may lead you in right direction for a fix. Using the Configuration tool may be helpfull.
http://blogs.msdn.com/lukaszp/archive/2006/05/18/601340.aspx
Sunday, March 11, 2012
Deploying Reports
this is about two related issues...
We tried to deploy by backing up the ReportServer DB on my XP dev box and
restoring over an existing ReportServer DB on a Server 2003 box. After the
restore, when trying to go to /localhost/reports we got "login failed for
'NT AUTHORITY\NETWORK SERVICE'. We then added that user to the ReportServer
Database. Then we got 'Cannot read ReportServer DB. Found Version unknown
expected Versions C.0.8.40.
So the first question is what went wrong?
The second question is: How are we supposed to deploy reports from an XP dev
box to a Server 2003 box? It can't be database backups and restores - it
must be by report but I can't find it in the docs. Can you point this out
in the docs or tell me how?
--
Regards,
Gary BlakelyHi Gary,
Thank you for your posting!
For the first issue, I think the root cause is that your Report Server
database is not match the Reporting Services binaries. The binaries are SQL
2005 and I wonder what's your Report Server databases in the dev box. If
it's SQL 2000, please follow the article to migrate the report server
database to SQL 2005:
If not, please make sure the Reporting Services is the same with the
service pack.
If your reporting services on your dev box is SQl 2005 SP1, I think you
need to upgrade your SQL 2005 on your server box to SP1 and then restore
the database.
For the deploy issue, as I mentioned above, you could use the backup and
restore to move all the reports to another server. But, the reporting
services should be the same.
Also, I think the best way for you is keep the report design project and
use the project to deploy the reports again.
Hope this will be helpful! If you have any questions or concerns, please
feel free to let me know.
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.|||Wei,
All boxes are using ss2005.
I think that restoring over the ReportServer db on the target machine is not
a good idea because several programers will be deploying reports to that
machine and we can't wipe out work already on the target reporserver.
Can I deploy to another Server on the network. Seems that should be the way
to deploy.
But a second issue is the difference between XP and Server 2003. XP uses
MACHINE\ASPNET and Server2003 uses 'NT AUTHORITY\NETWORK SERVICE'. If we
don't use restore this should not be an issue because we are just deploying
reports. no?
Gary
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:8LOq3oAnGHA.4632@.TK2MSFTNGXA01.phx.gbl...
> Hi Gary,
> Thank you for your posting!
> For the first issue, I think the root cause is that your Report Server
> database is not match the Reporting Services binaries. The binaries are
> SQL
> 2005 and I wonder what's your Report Server databases in the dev box. If
> it's SQL 2000, please follow the article to migrate the report server
> database to SQL 2005:
> If not, please make sure the Reporting Services is the same with the
> service pack.
> If your reporting services on your dev box is SQl 2005 SP1, I think you
> need to upgrade your SQL 2005 on your server box to SP1 and then restore
> the database.
> For the deploy issue, as I mentioned above, you could use the backup and
> restore to move all the reports to another server. But, the reporting
> services should be the same.
> Also, I think the best way for you is keep the report design project and
> use the project to deploy the reports again.
> Hope this will be helpful! If you have any questions or concerns, please
> feel free to let me know.
> 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.
>|||Hi Gary,
Thank you for the reply.
Deploy the report from your Visual Studio will be OK. The user is not a
issue. You could deploy the report from your designer to the server.
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.|||Hi Gary,
How is everything going? Please feel free to let me know if you need any
assistance.
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.
We tried to deploy by backing up the ReportServer DB on my XP dev box and
restoring over an existing ReportServer DB on a Server 2003 box. After the
restore, when trying to go to /localhost/reports we got "login failed for
'NT AUTHORITY\NETWORK SERVICE'. We then added that user to the ReportServer
Database. Then we got 'Cannot read ReportServer DB. Found Version unknown
expected Versions C.0.8.40.
So the first question is what went wrong?
The second question is: How are we supposed to deploy reports from an XP dev
box to a Server 2003 box? It can't be database backups and restores - it
must be by report but I can't find it in the docs. Can you point this out
in the docs or tell me how?
--
Regards,
Gary BlakelyHi Gary,
Thank you for your posting!
For the first issue, I think the root cause is that your Report Server
database is not match the Reporting Services binaries. The binaries are SQL
2005 and I wonder what's your Report Server databases in the dev box. If
it's SQL 2000, please follow the article to migrate the report server
database to SQL 2005:
If not, please make sure the Reporting Services is the same with the
service pack.
If your reporting services on your dev box is SQl 2005 SP1, I think you
need to upgrade your SQL 2005 on your server box to SP1 and then restore
the database.
For the deploy issue, as I mentioned above, you could use the backup and
restore to move all the reports to another server. But, the reporting
services should be the same.
Also, I think the best way for you is keep the report design project and
use the project to deploy the reports again.
Hope this will be helpful! If you have any questions or concerns, please
feel free to let me know.
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.|||Wei,
All boxes are using ss2005.
I think that restoring over the ReportServer db on the target machine is not
a good idea because several programers will be deploying reports to that
machine and we can't wipe out work already on the target reporserver.
Can I deploy to another Server on the network. Seems that should be the way
to deploy.
But a second issue is the difference between XP and Server 2003. XP uses
MACHINE\ASPNET and Server2003 uses 'NT AUTHORITY\NETWORK SERVICE'. If we
don't use restore this should not be an issue because we are just deploying
reports. no?
Gary
"Wei Lu [MSFT]" <weilu@.online.microsoft.com> wrote in message
news:8LOq3oAnGHA.4632@.TK2MSFTNGXA01.phx.gbl...
> Hi Gary,
> Thank you for your posting!
> For the first issue, I think the root cause is that your Report Server
> database is not match the Reporting Services binaries. The binaries are
> SQL
> 2005 and I wonder what's your Report Server databases in the dev box. If
> it's SQL 2000, please follow the article to migrate the report server
> database to SQL 2005:
> If not, please make sure the Reporting Services is the same with the
> service pack.
> If your reporting services on your dev box is SQl 2005 SP1, I think you
> need to upgrade your SQL 2005 on your server box to SP1 and then restore
> the database.
> For the deploy issue, as I mentioned above, you could use the backup and
> restore to move all the reports to another server. But, the reporting
> services should be the same.
> Also, I think the best way for you is keep the report design project and
> use the project to deploy the reports again.
> Hope this will be helpful! If you have any questions or concerns, please
> feel free to let me know.
> 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.
>|||Hi Gary,
Thank you for the reply.
Deploy the report from your Visual Studio will be OK. The user is not a
issue. You could deploy the report from your designer to the server.
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.|||Hi Gary,
How is everything going? Please feel free to let me know if you need any
assistance.
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.
Saturday, February 25, 2012
deploy SSIS package to server
Ok, I created SSIS packages on my local box. All of my packages are using config files for the db connections and other configurations that'll be changed per environment. My question is how do I deploy the .dstx file and the associated config file to the servers?
Right now I'm running the packages in BIDS as I create them. I now want to run them on an actual server
One way is to map a drive (or just open a remote folder) to the server, and then copy the files there.I suggest you create a folder on the server to hold the SSIS stuff. From there you can create subfolders if you desire.|||
would I need to create folders for each package or no? How will the SSIS package now what config file is assocaited with it?
|||
IGotyourdotnet wrote:
would I need to create folders for each package or no? How will the SSIS package now what config file is assocaited with it?
You don't need to create a folder for each package, though that decision is up to you.
In the package (control flow, right click, package configurations), you specify which configuration file to use.
Friday, February 24, 2012
Deploy Solution brings up a login box
Login box shows a server ashttp://localhost/reports (could be wrong, I don't kow but that's what I put in the property for that)
Then it wants a user name and password. I've tried a few logons but it doesn't accept them.
What is the problem here?
Disregard. reports needs to be reportserver.Deploy Package Problem
I have a package that runs fine on my dev box. I deploy it to another server and run it by right-clicking and choosing run. I get an error saying it was unable to log in to the server.(Log in failed for user 'myuser') I am using sql authenication and the connection string says persist security info = true. So where is that password stored? Did I miss something when I deployed?
(I have other connections in the package that are windows auth and they work fine)
Data Source=myserver;User ID=myuser;Initial Catalog=Staging;Provider=SQLNCLI.1;Persist Security Info=True;Auto Translate=False;
(I am just trying to get it to run on the other server, I know I may have other issues when I try to run it under sql agent)
Thx
Who is it package running as on the second server and what is the Package's protection level?|||Thanks for the reply jaegd.
It is running under my id but I am using sql authentication to connect to a remote server and that is where my problem is not with the local server. The part of the package that connects locally under my id works fine, it's only when trying to connect to the remote sever that the password is not being used, I think it is trying to log in with a blank pwd.
Package protection is : EncryptSensitiveWithUserKey
|||I had the same issue. Even on my own machine, no matter how many times I checked "[ ] Save my Password" it would continue to forget it and fail the connections (all 100+).
I finally have resorted to Windows Authentication which I've heard now from several sources is the preferred / encouraged method. Once I switched all my OLE DB connections over to it, it worked fine. Problem is, you have to have permission on the remote server.
I call BUG.
|||Found this thread: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=193221&SiteID=1
Which basically says to set your package protection level to DontSaveSensitive and use package configurations for storing passwords, server names, etc.
Simple works for me, only small concern is the passwords are not encrypted (maybe they can be somehow through SSIS) but I can live with it..
deploy pacakge - what files have to go?
I'm getting ready to deploy my SSIS packages to a real server (woohoo) after testing on my local SQL box. What files have to be deployed to the SQL server? I'm creating a folder for each package (easier for these guys to maintain when my contract is up). Does only the .dtsx and .dtsConfig file go or is there any other files that have to be copied over to the SQL server?
Only the dtsx files need to go. You can deploy individually or you can set the create deployment utility as a Project Property and then just double click the manifest to deploy all of them at once. You shouldn't have to manually copy any files.
|||Ok, even though I have a .dtsconfig file defined for them, that doesn't have to go to the servers?
As for the .dtsx file, I see one in the Bin folder of my project and one outside of the bin folder which one goes or does the deploy utility grab the correct one?
|||
In the Deploymet folder there should be a file with the extension .SSISDeploymentManifest. Double click on that. It will deploy the files from the Deployment folder.
If you don't have a Deployment folder, right click on the project and choose properties.
In the properties page, click on the Deployment Utility entry (middle one) and change create deployment utility to True.
|||Ok, thanks, I'll look into it. This is the first for this for me, so. .
|||If you want to include the configuration settings from the .dtsconfig file then you should deploy it. I am 99.9 % certain that you want to include it.
The deploy utility will grab the correct .dtsx file.
|||
From my experience (not very much though 
Its just my thought.
Thanks
Sunday, February 19, 2012
Deploy Asks for Username and Password - Can't Deploy
Today I installed SP2 on my client and rebooted.
Since then, when I try to deploy from Visual Studio, I get a box that pops
up that asks for a username and password. I tried entering everything under
the sun but I can't get past it.
The user I am logged in as is part of the Administrators group on the RS
server. Beyond that, none of the server config has changed.
What is going on here? I can't deploy!
Thanks,
HunterI experience this problem too. I even created a new user name under the
security properties tab, for my user account, "Administrator"
"Hunter Hillegas" wrote:
> Today I installed SP2 on my client and rebooted.
> Since then, when I try to deploy from Visual Studio, I get a box that pops
> up that asks for a username and password. I tried entering everything under
> the sun but I can't get past it.
> The user I am logged in as is part of the Administrators group on the RS
> server. Beyond that, none of the server config has changed.
> What is going on here? I can't deploy!
> Thanks,
> Hunter|||Try this
"create a DWORD entry called DisableLoopbackCheck to
HKLM\System\CurrentControlSet\Control\Lsa. Set this key to a value of 1"
I hope, this helps.
Barbaros Saglamtimur
MCDBA, MCAD
"Chiara" <Chiara@.discussions.microsoft.com> wrote in message
news:66581066-291D-47A1-A577-38E89BA9E6A3@.microsoft.com...
>I experience this problem too. I even created a new user name under the
> security properties tab, for my user account, "Administrator"
> "Hunter Hillegas" wrote:
>> Today I installed SP2 on my client and rebooted.
>> Since then, when I try to deploy from Visual Studio, I get a box that
>> pops
>> up that asks for a username and password. I tried entering everything
>> under
>> the sun but I can't get past it.
>> The user I am logged in as is part of the Administrators group on the RS
>> server. Beyond that, none of the server config has changed.
>> What is going on here? I can't deploy!
>> Thanks,
>> Hunter|||Thanks for posting this. I gave it a try but I am still greeted with the same
password prompt that accepts no credentials.
Any other ideas out there?
"saglamtimur" wrote:
> Try this
> "create a DWORD entry called DisableLoopbackCheck to
> HKLM\System\CurrentControlSet\Control\Lsa. Set this key to a value of 1"
>
> I hope, this helps.
> Barbaros Saglamtimur
> MCDBA, MCAD
>
> "Chiara" <Chiara@.discussions.microsoft.com> wrote in message
> news:66581066-291D-47A1-A577-38E89BA9E6A3@.microsoft.com...
> >I experience this problem too. I even created a new user name under the
> > security properties tab, for my user account, "Administrator"
> >
> > "Hunter Hillegas" wrote:
> >
> >> Today I installed SP2 on my client and rebooted.
> >>
> >> Since then, when I try to deploy from Visual Studio, I get a box that
> >> pops
> >> up that asks for a username and password. I tried entering everything
> >> under
> >> the sun but I can't get past it.
> >>
> >> The user I am logged in as is part of the Administrators group on the RS
> >> server. Beyond that, none of the server config has changed.
> >>
> >> What is going on here? I can't deploy!
> >>
> >> Thanks,
> >> Hunter
>
>
Since then, when I try to deploy from Visual Studio, I get a box that pops
up that asks for a username and password. I tried entering everything under
the sun but I can't get past it.
The user I am logged in as is part of the Administrators group on the RS
server. Beyond that, none of the server config has changed.
What is going on here? I can't deploy!
Thanks,
HunterI experience this problem too. I even created a new user name under the
security properties tab, for my user account, "Administrator"
"Hunter Hillegas" wrote:
> Today I installed SP2 on my client and rebooted.
> Since then, when I try to deploy from Visual Studio, I get a box that pops
> up that asks for a username and password. I tried entering everything under
> the sun but I can't get past it.
> The user I am logged in as is part of the Administrators group on the RS
> server. Beyond that, none of the server config has changed.
> What is going on here? I can't deploy!
> Thanks,
> Hunter|||Try this
"create a DWORD entry called DisableLoopbackCheck to
HKLM\System\CurrentControlSet\Control\Lsa. Set this key to a value of 1"
I hope, this helps.
Barbaros Saglamtimur
MCDBA, MCAD
"Chiara" <Chiara@.discussions.microsoft.com> wrote in message
news:66581066-291D-47A1-A577-38E89BA9E6A3@.microsoft.com...
>I experience this problem too. I even created a new user name under the
> security properties tab, for my user account, "Administrator"
> "Hunter Hillegas" wrote:
>> Today I installed SP2 on my client and rebooted.
>> Since then, when I try to deploy from Visual Studio, I get a box that
>> pops
>> up that asks for a username and password. I tried entering everything
>> under
>> the sun but I can't get past it.
>> The user I am logged in as is part of the Administrators group on the RS
>> server. Beyond that, none of the server config has changed.
>> What is going on here? I can't deploy!
>> Thanks,
>> Hunter|||Thanks for posting this. I gave it a try but I am still greeted with the same
password prompt that accepts no credentials.
Any other ideas out there?
"saglamtimur" wrote:
> Try this
> "create a DWORD entry called DisableLoopbackCheck to
> HKLM\System\CurrentControlSet\Control\Lsa. Set this key to a value of 1"
>
> I hope, this helps.
> Barbaros Saglamtimur
> MCDBA, MCAD
>
> "Chiara" <Chiara@.discussions.microsoft.com> wrote in message
> news:66581066-291D-47A1-A577-38E89BA9E6A3@.microsoft.com...
> >I experience this problem too. I even created a new user name under the
> > security properties tab, for my user account, "Administrator"
> >
> > "Hunter Hillegas" wrote:
> >
> >> Today I installed SP2 on my client and rebooted.
> >>
> >> Since then, when I try to deploy from Visual Studio, I get a box that
> >> pops
> >> up that asks for a username and password. I tried entering everything
> >> under
> >> the sun but I can't get past it.
> >>
> >> The user I am logged in as is part of the Administrators group on the RS
> >> server. Beyond that, none of the server config has changed.
> >>
> >> What is going on here? I can't deploy!
> >>
> >> Thanks,
> >> Hunter
>
>
Subscribe to:
Posts (Atom)