Monday, March 26, 2012
Is it possible to hide the report parameters after click on the view report button?
after selecting all the report paramters and click on the view report
button, i need to turn off or hide the report parameters.
please let me know is it possible to implement to do this.
any suggesstion
Thanks
VinodThere is a button the right side of the page of the reports browser
that look like to arrows on top of each other, click that and it will
hide the parameters. There are actually two sets, one for the
parameters and one for the web page header. Hope that helps.
Vinod wrote:
> i am working in SQL Reporting services 2005. i had a requirement that
> after selecting all the report paramters and click on the view report
> button, i need to turn off or hide the report parameters.
> please let me know is it possible to implement to do this.
> any suggesstion
> Thanks
> Vinod|||Thanks for the reply Kerrie.
i have seen the hide button icon in the report layout.but my
requirement is that i need to hide the parameters when i click on the
view report button in the report layout after selecting the all the
report parameters.
if user wants to modify the criteria again, he needs to click on the
hide icon in the report layout. then select the criteria and view the
report.
please let me know if you are not clear
Thanks
vinod
Kerrie wrote:
> There is a button the right side of the page of the reports browser
> that look like to arrows on top of each other, click that and it will
> hide the parameters. There are actually two sets, one for the
> parameters and one for the web page header. Hope that helps.
>
> Vinod wrote:
> > i am working in SQL Reporting services 2005. i had a requirement that
> > after selecting all the report paramters and click on the view report
> > button, i need to turn off or hide the report parameters.
> >
> > please let me know is it possible to implement to do this.
> >
> > any suggesstion
> >
> > Thanks
> > Vinod|||I'm pretty sure there's no function like that in RS out of the box. But I'm
thinking that if you can modify the View Report button's code, you could add
a java script that redirects to a url with parameters toolbar=false and the
chosen parameters. You'd have to tweek the RS GUI to do it, and I don't know
how easy that is.
Alternatively, create a aspx. page that creates the parameters to be chosen,
and send the users to a report using the same paramtererized url as
suggested above.
Kaisa M. Lindahl Lervik
"Vinod" <vinodsh_82@.hotmail.com> wrote in message
news:1161352815.498895.319680@.h48g2000cwc.googlegroups.com...
> Thanks for the reply Kerrie.
> i have seen the hide button icon in the report layout.but my
> requirement is that i need to hide the parameters when i click on the
> view report button in the report layout after selecting the all the
> report parameters.
> if user wants to modify the criteria again, he needs to click on the
> hide icon in the report layout. then select the criteria and view the
> report.
> please let me know if you are not clear
> Thanks
> vinod
>
> Kerrie wrote:
>> There is a button the right side of the page of the reports browser
>> that look like to arrows on top of each other, click that and it will
>> hide the parameters. There are actually two sets, one for the
>> parameters and one for the web page header. Hope that helps.
>>
>> Vinod wrote:
>> > i am working in SQL Reporting services 2005. i had a requirement that
>> > after selecting all the report paramters and click on the view report
>> > button, i need to turn off or hide the report parameters.
>> >
>> > please let me know is it possible to implement to do this.
>> >
>> > any suggesstion
>> >
>> > Thanks
>> > Vinod
>|||Thanks for the reply Kaisa.
i am not creating a aspx page for criteria. i have added 15 report
parameters in the report layout iteself. everything is fine upto this
point.
but my client requriment is that we dont want to show the report
parameters in the report layout after clicking on the view report
button. it should be hided.
let me know is it possible.
Thanks
Vinod
Kaisa M. Lindahl Lervik wrote:
> I'm pretty sure there's no function like that in RS out of the box. But I'm
> thinking that if you can modify the View Report button's code, you could add
> a java script that redirects to a url with parameters toolbar=false and the
> chosen parameters. You'd have to tweek the RS GUI to do it, and I don't know
> how easy that is.
> Alternatively, create a aspx. page that creates the parameters to be chosen,
> and send the users to a report using the same paramtererized url as
> suggested above.
> Kaisa M. Lindahl Lervik
> "Vinod" <vinodsh_82@.hotmail.com> wrote in message
> news:1161352815.498895.319680@.h48g2000cwc.googlegroups.com...
> > Thanks for the reply Kerrie.
> >
> > i have seen the hide button icon in the report layout.but my
> > requirement is that i need to hide the parameters when i click on the
> > view report button in the report layout after selecting the all the
> > report parameters.
> >
> > if user wants to modify the criteria again, he needs to click on the
> > hide icon in the report layout. then select the criteria and view the
> > report.
> >
> > please let me know if you are not clear
> >
> > Thanks
> > vinod
> >
> >
> > Kerrie wrote:
> >> There is a button the right side of the page of the reports browser
> >> that look like to arrows on top of each other, click that and it will
> >> hide the parameters. There are actually two sets, one for the
> >> parameters and one for the web page header. Hope that helps.
> >>
> >>
> >> Vinod wrote:
> >> > i am working in SQL Reporting services 2005. i had a requirement that
> >> > after selecting all the report paramters and click on the view report
> >> > button, i need to turn off or hide the report parameters.
> >> >
> >> > please let me know is it possible to implement to do this.
> >> >
> >> > any suggesstion
> >> >
> >> > Thanks
> >> > Vinod
> >
Is it possible to have SQL send an email out based on a value in a table?
I'm working on a trouble ticket application and would like to add one more bit of functionality to the system:
When a new trouble ticket is created via the application front end (ASP.NET web application) the system sends an email to an appropiate party indicating that a new ticekt has been issued and needs to be responded to. The user must then log into the system to see the new ticket. The ticket is of course stored in the database (SQL Sever 2000). My question is, whether it is possible to tell SQL server to automatically send emails on a set time interval as long as their are tickets in the database that have a status of new?
ThanksThere is a SQL Server extended stored procedure, xp_Sendmail, that will allow your SQL code to send mail (presuming the SQL Mail agent is configured and running).|||You can also use CDONTS from a stored procedure if you don't have SQL Mail installed - http://support.microsoft.com/view/tn.asp?kb=312839|||Thanks all. I have a procedure that uses CDONTS and it works fine. now I gotta figure out hot to schedule it to run based on a field in a database. But hopefully that should be easy.
Wendell|||Hi
This KB is not anymore available online. Can you provide the details for this?
Cesar|||Here'sanother article on the same topic.
Regards,
Xander
Friday, March 23, 2012
Is it possible to dynamically create columns in a table in SSRS
Hi,
I have a sproc that returns somevalues and everything is working fine... and in my reports i am assigning the header data (in a detail column) based on the some feilds in the sproc... and there around 20 feilds that i want to show... but at a given time i am pretty sure that there wont be more than 10 fields that will have data.
So is it possible that show only the columns that have data in it and sometimes if there is less that 5 - 6 fields.. i want to realign the widths of the column in those tables without shrinking the size of the Table...
any help is appreciated..
Regards
Karen
Hi,
So is it possible that show only the columns that have data in it and sometimes if there is less that 5 - 6 fields.. i want to realign the widths of the column in those tables without shrinking the size of the Table...
If there's no record in one of your row, you can use =IsNothing(Fields!productname.Value) filter your record. But if you want to hide the column that has no data, I suggest you to handle these works in your data accessing modular. For example, if you check one of your column is empty, just remove the column in your record set, so the column would not show in the report.
Thanks.
Jin,
Thanks for your response.. what do u mean by remove the column from the recordset... cause i am populating the Reports using a stored procedure and sometimes... there may be some data or not..
Can u pls give me code snipet or an example
Regards
Karen
|||Hi,
if you check one of your column is empty, just remove the column in your record set, so the column would not show in the report.
Here's the sample code, suppose you have two fields, Sp and Hd. If there's no data in Hd field of your return set, then only Sp field would been selected.
DECLARE @.NULLCOUNTINTSELECT @.NULLCOUNT =COUNT(*)FROM MatrixCapitalWHERE MatrixCapital.Spisnot nullif @.NULLCOUNT=0BEGIN SELECT MatrixCapital.HdFROM MatrixCapitalEND ELSEBEGIN SELECT MatrixCapital.Hd,MatrixCapital.SpFROM MatrixCapitalENDThanks.|||
Jin,
Thanks a lot for your answer so this mean that if i have more 5 - 6 columns NULL... i have check for each column in the NULL count and then prob union for each feild so that my end resultset will be columns that has data in them?
I have another question too.. if i have a table variable like
Declare @.tbl table
(
tblid int indentity(1,1),
Col 1,
Col 2,
..,
Col n
)
Is it possible to have a variable column size depending on the number of entries in my select column like for example.. my if i have 10 columns in my select statement and in that 5 are null... so can just insert 5 rows to the table and then remove the remaining columns out.
Regards
Karen
|||
Hi,
i have check for each column in the NULL count and then prob union for each feild so that my end resultset will be columns that has data in them?
Yes, that's right.
Is it possible to have a variable column size depending on the number of entries in my select column like for example..
Based on my knowledge, another way i can see is to use CASE WHEN clause in your SQL, but it still requires you to give differrent sql statments accoring to the "isNUll" result of a column.
Thanks.
sqlIs it possible to disable Poison Message Detection?
I'm using the Service Broker to parallize my processes (I know that the Service Broker was not designed for that purpose), however it's working quite well.
I use the broker procedure to start procedures which all process all a part of the workload. When the procedure fails because of a lock timeout (or for that concern, for whatever reason), I rollback the transaction (which also roll back my message received on the queue so that it can be retried at a later time.). And this is where my problem lies, if there are 5 sequential rollbacks of messages then the poison message detection kicks in and disables the queue, stopping all the processing. :(
Is there a way to disable poison message detection? I have implemented my own stop-mechanism through a counter system on a per sub-task system so if I could disable poison message detection that would be ideal.
If this is not possible is there a way to turn the queue back on automatically so that it will continue processing the messages on the queue?
Cheers,
Peter.
Not sure if this helps your situation but you could do a SAVE TRANSACTION after you have received it off the queue.
Then, if whatever condition happens for it to rollback you can rollback to the save point, that way all work will be rolled back but the poison message is committed off the queue, you could also write the message to a table afetrwards, that way your queue will keep working and you can save the poison message to check them out later, and possibly put a notification trigger on the poison message table so that you know when they happen so you can check them out, hope that helps ?
Thanx
|||In SQL Server 2005 is not possible to disable poison message support. The main problem with disabling poison message detection is that when something goes wrong and a real poison message comes into a production system, it takes the service down. We really encourage developers to avoid using rollbacks in activated procedures.
For instance, in your case, maybe is better to save the message being processed (e.g. into a table, or turn on message retention to use the queue itself w/o the need for a table) and then send yourself a timer message (BEGIN CONVERSATION TIMER with a small delay) and commit. When the timer fires a message is sent to your own service and you are going to be activated again. the activated procedure reacts to the timer message by looking up the saved message and trying to process it again. If it fails again, set a new timer ang commit. This way you can set up a more reasonable retry policy than rollback and retry immedeatly.
As about a way to turn the queue back on automatically, yes, there is a way. When a queue is deactivated, it can generate an event notification:
CREATE EVENT NOTIFICATION [QueueDisabled]
ON QUEUE [<queue name>]
FOR BROKER_QUEUE_DISABLED
TO SERVICE 'QueueDisabledServiceHandler', 'current database';
HTH,
~ Remus
I have the following code for reactivation:
CREATE QUEUE q_task_detail_receive_disabled_handler
CREATE SERVICE s_task_detail_receive_disbaled_handler ON QUEUE q_task_detail_receive_disabled_handler
CREATE EVENT NOTIFICATION q_task_detail_receive_disabled
ON QUEUE q_task_detail_receive
FOR BROKER_QUEUE_DISABLED
TO SERVICE 's_task_detail_receive_disbaled_handler', 'current database';
create procedure p_enable_queues
as
begin
ALTER queue q_task_detail_receive WITH STATUS = ON
end
go
ALTER QUEUE q_task_detail_receive_disabled_handler
WITH ACTIVATION (
STATUS = ON, -- Activation turned on
PROCEDURE_NAME = p_enable_queues, -- The name of the proc to process messages for this queue
MAX_QUEUE_READERS = 1, -- The maximum number of copies of the proc to start
EXECUTE AS SELF -- Start the procedure as the user who created the queue.
);|||
Is the notification being delivered into q_task_disabled_handler?
You must RECEIVE from q_task_receive_disabled_handler in the p_enable_queues. This is a general rule for activated procedures, they must RECEIVE from the queue, even if they don't care about the message.
HTH,
~ Remus
Wednesday, March 21, 2012
Is it possible to create the columns of a #Temp table base on a query result?
I’ve been trying without success something like this…
CREATE TABLE #table
(
(SELECT MAX(Column) FROM Table) varchar(50)
)I'm working with SQL 2005; thank you for any help in advance.
Not quite like that.
You can SELECT ... INTO.
In the process, you need to provide a column Name for any computed or derived columns, and you can change the datatype.
Something like this:
Code Snippet
USE Northwind
GO
SELECT cast( max( EmployeeID ) AS decimal(6,2)) AS MaxEmp
INTO #MyTable
FROM Employees
There are 2 options,
Create Table #Table (
ColumnValue Varchar(50)
);
Insert Into #Table
SELECT MAX(Column) FROM TableName;
--OR
SELECT Cast(MAX(Column) as Varchar(50)) ColumnValue Into #Table FROM TableName;
|||Thank you for the help provided so far. Another question on the same subject. How can the Column name be assigned dynamically after a query result? Thanks.|||
You should use the aliase name. if you failed to give the aliase name for the expression sql server thow an error says that "No column was specified for column n on tablename".
Code Snippet
Select Max(Column) as MaxColumn Into NewTable From OldTable
Select Max(Column) MaxColumn into Newtable From OldTable
|||
As indicated above, No.
My apologies, I guess this statement was not clear enough.
sql
In the process, you need to provide a column Name for any computed or derived columns...
Is it possible to convert T-SQL 2005 to T-SQL 2000
I am working with the Web Service Software Factory and I have created my stored procedures that I will be needing. The problem is that when I try to apply the SP's to the database, I receive errors regarding the syntax. I am using SQL Server 2000 and it generates the script in 2005 T-SQL format. The script in 2005 is quite different from 2000 and I am not sure if converting it is even possible (eg. no try catch equivalent in 2000 and new error handling ). I searched msdn to check if I could specify the script version in WSSF, but I could not find anything. Any suggestions as to how I might solve this without purchasing SQL Server 2005?
The Web Service Software Factory had created this sql file that included the following function that is used throughout the file:
Code Snippet
IF NOT EXISTS (SELECT NAME FROM dbo.sysobjects WHERE TYPE = 'P' AND NAME = 'RethrowError')
BEGIN
EXEC('CREATE PROCEDURE [dbo].RethrowError AS RETURN')
END
GO
ALTER PROCEDURE RethrowError AS
/* Return if there is no error information to retrieve. */
IF ERROR_NUMBER() IS NULL
RETURN;
DECLARE
@.ErrorMessage NVARCHAR(4000),
@.ErrorNumber INT,
@.ErrorSeverity INT,
@.ErrorState INT,
@.ErrorLine INT,
@.ErrorProcedure NVARCHAR(200);
/* Assign variables to error-handling functions that
capture information for RAISERROR. */
SELECT
@.ErrorNumber = ERROR_NUMBER(),
@.ErrorSeverity = ERROR_SEVERITY(),
@.ErrorState = ERROR_STATE(),
@.ErrorLine = ERROR_LINE(),
@.ErrorProcedure = ISNULL(ERROR_PROCEDURE(), '-');
/* Building the message string that will contain original
error information. */
SELECT @.ErrorMessage =
N'Error %d, Level %d, State %d, Procedure %s, Line %d, ' +
'Message: '+ ERROR_MESSAGE();
/* Raise an error: msg_str parameter of RAISERROR will contain
the original error information. */
RAISERROR(@.ErrorMessage, @.ErrorSeverity, 1,
@.ErrorNumber, /* parameter: original error number. */
@.ErrorSeverity, /* parameter: original error severity. */
@.ErrorState, /* parameter: original error state. */
@.ErrorProcedure, /* parameter: original error procedure name. */
@.ErrorLine /* parameter: original error line number. */
);
GO
And the error I receive is this ( I added 'machine\instance' to make it more generic):
Code Snippet
Msg 195, Level 15, State 10, Server Machine\Instance, Procedure RethrowError, Line 4
'ERROR_NUMBER' is not a recognized function name.
Msg 195, Level 15, State 10, Server Machine\Instance, Procedure RethrowError, Line 19
'ERROR_NUMBER' is not a recognized function name.
Msg 195, Level 15, State 10, Server Machine\Instance, Procedure RethrowError, Line 30
'ERROR_MESSAGE' is not a recognized function name.
Msg 170, Level 15, State 1, Server Machine\Instance, Procedure InsertUsers, Line 29
Line 29: Incorrect syntax near 'TRY'.
Msg 170, Level 15, State 1, Server Machine\Instance, Procedure InsertUsers, Line 37
Line 37: Incorrect syntax near 'TRY'.
Msg 156, Level 15, State 1, Server Machine\Instance, Procedure InsertUsers, Line 41
Incorrect syntax near the keyword 'END'.
Msg 156, Level 15, State 1, Server Machine\Instance, Procedure InsertUsers, Line 44
Incorrect syntax near the keyword 'END'.
Msg 170, Level 15, State 1, Server Machine\Instance, Procedure UpdateUsers, Line 31
Line 31: Incorrect syntax near 'TRY'.
Msg 170, Level 15, State 1, Server Machine\Instance, Procedure UpdateUsers, Line 40
Line 40: Incorrect syntax near 'TRY'.
Msg 156, Level 15, State 1, Server Machine\Instance, Procedure UpdateUsers, Line 44
Incorrect syntax near the keyword 'END'.
Msg 156, Level 15, State 1, Server Machine\Instance, Procedure UpdateUsers, Line 47
Incorrect syntax near the keyword 'END'.
The other errors involving the try-catch and end revolve around the try-catch syntax where it does not recognize the rethrowerror function.
Code Snippet
BEGIN TRY
Do Something
END TRY
BEGIN CATCH
EXEC RethrowError;
END CATCH
Any suggestions as to how I could convert this without having to rewrite the sql file generated the project tools? Thanks in advance.
You will have to remove the exception handling code (it is new in SQL Server 2005). You need to also remove references to the ERROR* functions. Only @.@.ERROR was available before.|||That seems so easy. I cant believe I didnt think of that on my own! Thanks for your help.Monday, March 19, 2012
is it possible to call LogonUser with out SSL?
I am working with RS form authentication.I am fallowing MSDN whitepages.
my Questions r
(1)
Is it possble to work with customsecurity without Using the Web Service
implementation?if so how can i ?
If no should i have adminsrtaive privillages on IIS
(2) is it possible to call LogonUser with out SSL?
could anybody help me
thanksYes, you can call LogonUser without SSL, but it's not recommended.
I'm not sure what's leading you to ask if you can use customsecurity without
the Web Service implementation.
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"gundui" <gundui@.discussions.microsoft.com> wrote in message
news:74B15656-4906-4CDA-BA8B-E5513F7F2731@.microsoft.com...
> Hi .
> I am working with RS form authentication.I am fallowing MSDN whitepages.
> my Questions r
> (1)
> Is it possble to work with customsecurity without Using the Web Service
> implementation?if so how can i ?
> If no should i have adminsrtaive privillages on IIS
> (2) is it possible to call LogonUser with out SSL?
> could anybody help me
> thanks
>|||In that whitepaper it does not specifically say that it is required,
however, the MSDN page on the LogonUser method states in many locations
that SSL is required with the LogonUser method. Could you explain
where you read that it was not requiered?
Thanks
Jeff A. Stucker wrote:
> Yes, you can call LogonUser without SSL, but it's not recommended.
> I'm not sure what's leading you to ask if you can use customsecurity
without
> the Web Service implementation.
> --
> Cheers,
> '(' Jeff A. Stucker
> \
> Business Intelligence
> www.criadvantage.com
> ---
> "gundui" <gundui@.discussions.microsoft.com> wrote in message
> news:74B15656-4906-4CDA-BA8B-E5513F7F2731@.microsoft.com...
> > Hi .
> > I am working with RS form authentication.I am fallowing MSDN
whitepages.
> >
> > my Questions r
> > (1)
> > Is it possble to work with customsecurity without Using the Web
Service
> > implementation?if so how can i ?
> >
> > If no should i have adminsrtaive privillages on IIS
> >
> > (2) is it possible to call LogonUser with out SSL?
> >
> > could anybody help me
> >
> > thanks
> >
> >|||The documentation has an error. :-)
--
Cheers,
'(' Jeff A. Stucker
\
Business Intelligence
www.criadvantage.com
---
"Will" <wlansing@.rlcarriers.com> wrote in message
news:1109701130.943200.167070@.z14g2000cwz.googlegroups.com...
> In that whitepaper it does not specifically say that it is required,
> however, the MSDN page on the LogonUser method states in many locations
> that SSL is required with the LogonUser method. Could you explain
> where you read that it was not requiered?
> Thanks
>
> Jeff A. Stucker wrote:
>> Yes, you can call LogonUser without SSL, but it's not recommended.
>> I'm not sure what's leading you to ask if you can use customsecurity
> without
>> the Web Service implementation.
>> --
>> Cheers,
>> '(' Jeff A. Stucker
>> \
>> Business Intelligence
>> www.criadvantage.com
>> ---
>> "gundui" <gundui@.discussions.microsoft.com> wrote in message
>> news:74B15656-4906-4CDA-BA8B-E5513F7F2731@.microsoft.com...
>> > Hi .
>> > I am working with RS form authentication.I am fallowing MSDN
> whitepages.
>> >
>> > my Questions r
>> > (1)
>> > Is it possble to work with customsecurity without Using the Web
> Service
>> > implementation?if so how can i ?
>> >
>> > If no should i have adminsrtaive privillages on IIS
>> >
>> > (2) is it possible to call LogonUser with out SSL?
>> >
>> > could anybody help me
>> >
>> > thanks
>> >
>> >
>
Monday, March 12, 2012
Is it possible for a subscriber to know.......
is there any sp can find out the replication is working properly?
thank you very much
You could have a look at the distribution agent's job to see if it is in
process - sp_helpjob or this link:
http://www.replicationanswers.com/Do...unningJobs.txt
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Friday, March 9, 2012
Is it not possible to nest IFs in a stored procedure
I have been working on this stored porcedure and now that I have it ready I get an error:
Msg 156, Level 15, State 1, Procedure UpdateFundAllocation, Line 38
Incorrect syntax near the keyword 'ELSE'.
Is it not possible to nest ifs the way I have them?
I greatly appreciate your help.
@.Receipt_IDInt,@.PRFund_IDInt,@.Fund_IDint,@.Amount_allocatedmoney,@.LastUpdatedatetime,@.LastUpdateBynvarchar(50)ASDeclare @.row_countintDeclare @.total_allocationsdecimal(18,2)Declare @.total_paymentsdecimal(18,2)SELECT @.row_count =COUNT(tblPayReceiptsFunds.Receipt_ID)FROMtblPayReceiptsFundsINNERJOIN tblPayReceiptsON tblPayReceiptsFunds.Receipt_ID = tblPayReceipts.Receipt_IDWHERE tblPayReceiptsFunds.Receipt_ID=@.Receipt_IDIF (@.row_count = 1)SELECT @.total_allocations = @.Amount_allocated, @.total_payments =Sum(tblPayReceipts.AmountPaid)FROM tblPayReceiptsFundsINNERJOIN tblPayReceiptsON tblPayReceiptsFunds.Receipt_ID = tblPayReceipts.Receipt_IDWHERE tblPayReceipts.Receipt_ID=@.Receipt_IDUPDATE tblPayReceiptsFundsSET [Fund_ID]=@.Fund_ID,[Amount_ALLOCATED]=@.Amount_ALLOCATED,LastUpdate=@.LastUpdate,LastUpdateBy=@.LastUpdateByWHERE [PRFund_ID]=@.PRFund_IDSELECT'Fund was allocated.'AS MESSAGEELSE BEGINSELECT @.total_allocations = (SUM(tblPayReceiptsFunds.Amount_allocated + @.Amount_allocated)), @.total_payments =Sum(tblPayReceipts.AmountPaid)FROM tblPayReceiptsFundsINNERJOIN tblPayReceiptsON tblPayReceiptsFunds.Receipt_ID = tblPayReceipts.Receipt_IDWHERE tblPayReceipts.Receipt_ID=@.Receipt_IDIF (@.total_allocations > @.total_payments)SELECT'You are attempting to allocate more to funds than your total payment.'AS MESSAGEELSE BEGINUPDATE tblPayReceiptsFundsSET [Fund_ID]=@.Fund_ID,[Amount_ALLOCATED]=@.Amount_ALLOCATED,LastUpdate=@.LastUpdate,LastUpdateBy=@.LastUpdateByWHERE [PRFund_ID]=@.PRFund_IDSELECT'Fund was allocated.'AS MESSAGEENDEND
Add a BEGIN and END to delineate the IF portions too
IF BEGIN--somethingENDELSE BEGIN IF BEGIN--somethingEND ELSE BEGIN--somethingEND END|||
You probably missed BEGIN after first IF clasue and END before First ELSE. Rememeber you have to have single block of code between IF and ELSE if you case you have SELECT, UPDATE and SELECT so you have to put BEGIN/END around thet to make them be a single block.
is it easy to amend an insert statement.
I am trying to amend an SQL insert statement but it is not working.
It is as follows can anyone tell me what i am doing wrong.
<asp:SqlDataSourceID="SqlDataSource1"runat="server"ConflictDetection="CompareAllValues"
ConnectionString="<%$ ConnectionStrings:ConnectionString2 %>"DeleteCommand="DELETE FROM [useridTest] WHERE [userID] = @.original_userID AND [userName] = @.original_userName AND [listCopy] = @.original_listCopy"
InsertCommand="INSERT INTO [useridTest] ([userID], [userName], [listCopy]) VALUES (<% user.ProviderUserKey.ToString() %>, @.userName, @.listCopy)"
Please add this to your SqlDataSource:OnInserting="SQLDataSource2_OnInserting"
and
<InsertParameters>
<asp:ParameterName="userID"Type="String"/>
</InsertParameters>Code:
protectedvoid SQLDataSource2_OnInserting(object sender,SqlDataSourceCommandEventArgs e){
e.Command.Parameters["@.userID"].Value =user.ProviderUserKey.ToString();}
Is it customary to reindex every night?
more production issues as I'm working in more complex businesses now.
One of the systems that we recently put into production is being
maintained by a non-DBA type whom I had a recent chat with. He told me
that they've found that the performance of the system seems to degrade
over a week as queries seem to take longer to execute as the week goes
on. So to combat the performance loss, he scheduled nightly reindexing
of the database.
Nightly reindexing of a database seems okay when you have the luxury
of not being a 24x7 business use application. However, I wouldn't have
ordinarily expected such harsh degredation over a weeks time period
(40 sec delays per query issued in some cases). This is a database
that is relatively more insert/update than select/report. I'm just
curious as to what your experiences have been? Have you found cases
where you've run indexing every night? If so why? If not, do you have
any opinions on what I should take a look at to investigate the
performance decrease?
Thanks in advance,
Osolage
Hi
"Osolage" wrote:
> I've been doing this DBA thing for a while. I'm having to deal with
> more production issues as I'm working in more complex businesses now.
> One of the systems that we recently put into production is being
> maintained by a non-DBA type whom I had a recent chat with. He told me
> that they've found that the performance of the system seems to degrade
> over a week as queries seem to take longer to execute as the week goes
> on. So to combat the performance loss, he scheduled nightly reindexing
> of the database.
> Nightly reindexing of a database seems okay when you have the luxury
> of not being a 24x7 business use application. However, I wouldn't have
> ordinarily expected such harsh degredation over a weeks time period
> (40 sec delays per query issued in some cases). This is a database
> that is relatively more insert/update than select/report. I'm just
> curious as to what your experiences have been? Have you found cases
> where you've run indexing every night? If so why? If not, do you have
> any opinions on what I should take a look at to investigate the
> performance decrease?
> Thanks in advance,
> Osolage
>
The amount of degredation is depending on the amount of change that the data
undergoes, therefore if there are a high number of transaction on the
database you may need to re-index more often. This can be made worse by
having poorly thought out fill factors or possibly even poor programming or
datatype selection.
Look at outputing what DBCC SHOWCONTIG gives before you re-index. You may
want to try and follow something similar to the example on the DBCC
SHOWCONTIG topic in books online which will only re-index when the
fragmentation gets above a certain level.
Also watch out for database shrinking (either auto or manual) which can also
cause fragmentation.
John
|||Yes, I've seen this.
Generally, there was some sloppy code and design, such that the
database ran well as long as it was squeezed into available RAM, but
with even a little fragmentation the missing indexes and bad plans
caused an exponential degradation in performance.
There was initially a lot of inserting to tables with (nonsequential)
GUID clustered PKs, after that was changed to simple identity int's
much of the problem went away.
So, it was split between some sloppy code, and some scalability issues
that called for specific redesigns.
Some of these problems can be a real pain to diagnose, when they only
occur on the production box, with full-scale data, and different
critical points because of a different processor count and different
RAM layout than any dev environments.
J.
On 29 Jan 2007 22:15:25 -0800, "Osolage" <osolage@.gmail.com> wrote:
>I've been doing this DBA thing for a while. I'm having to deal with
>more production issues as I'm working in more complex businesses now.
>One of the systems that we recently put into production is being
>maintained by a non-DBA type whom I had a recent chat with. He told me
>that they've found that the performance of the system seems to degrade
>over a week as queries seem to take longer to execute as the week goes
>on. So to combat the performance loss, he scheduled nightly reindexing
>of the database.
>Nightly reindexing of a database seems okay when you have the luxury
>of not being a 24x7 business use application. However, I wouldn't have
>ordinarily expected such harsh degredation over a weeks time period
>(40 sec delays per query issued in some cases). This is a database
>that is relatively more insert/update than select/report. I'm just
>curious as to what your experiences have been? Have you found cases
>where you've run indexing every night? If so why? If not, do you have
>any opinions on what I should take a look at to investigate the
>performance decrease?
>Thanks in advance,
>Osolage
|||Osolage wrote:
> I've been doing this DBA thing for a while. I'm having to deal with
> more production issues as I'm working in more complex businesses now.
> One of the systems that we recently put into production is being
> maintained by a non-DBA type whom I had a recent chat with. He told me
> that they've found that the performance of the system seems to degrade
> over a week as queries seem to take longer to execute as the week goes
> on. So to combat the performance loss, he scheduled nightly reindexing
> of the database.
> Nightly reindexing of a database seems okay when you have the luxury
> of not being a 24x7 business use application. However, I wouldn't have
> ordinarily expected such harsh degredation over a weeks time period
> (40 sec delays per query issued in some cases). This is a database
> that is relatively more insert/update than select/report. I'm just
> curious as to what your experiences have been? Have you found cases
> where you've run indexing every night? If so why? If not, do you have
> any opinions on what I should take a look at to investigate the
> performance decrease?
> Thanks in advance,
> Osolage
>
Depends on how the indexes are defined, how many inserts/updates across
index keys are occurring, etc. Also, as John mentioned, make sure
you're not shrinking the database - that will effectively "undo" any
reindexing that you've done.
Rather than rebuild EVERY index, consider rebuilding only those that are
fragmented. Here's a script to get you started. It needs a couple of
tweaks that I haven't gotten around to making, in particular it needs to
exclude index ID = 255, but it should get you started.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||You can look at Reorganize indexes and Reindex only highly fragmented
indexes.
BOL has good Example for it.
On Jan 30, 3:43 pm, JXStern <JXSternChange...@.gte.net> wrote:
> Yes, I've seen this.
> Generally, there was some sloppy code and design, such that the
> database ran well as long as it was squeezed into available RAM, but
> with even a little fragmentation the missing indexes and bad plans
> caused an exponential degradation in performance.
> There was initially a lot of inserting to tables with (nonsequential)
> GUID clustered PKs, after that was changed to simple identity int's
> much of the problem went away.
> So, it was split between some sloppy code, and some scalability issues
> that called for specific redesigns.
> Some of these problems can be a real pain to diagnose, when they only
> occur on the production box, with full-scale data, and different
> critical points because of a different processor count and different
> RAM layout than any dev environments.
> J.
> On 29 Jan 2007 22:15:25 -0800, "Osolage" <osol...@.gmail.com> wrote:
>
>
>
> - Show quoted text -
|||Hi, everyone,
I thank you for your comments so far. They validate my suspicions.
The procedures for checking index fragmentation and what-not can be
very tedious. This is something I've traditionally avoided except in
serious cases, because of the tedium. I'd be more inclined to dive in
if there are tools that help speed up the discovery of problem spots.
Have any of you used any tools to help speed up the research or to
even automate the discovery of problemmatic indexes? Please share or
link to your experiences if you are willing to share. I would love to
learn from you as it will make my job easier.
Sincere thanks,
Osoalge
|||On Feb 5, 4:38 pm, "Osolage" <osol...@.gmail.com> wrote:
> Hi, everyone,
> I thank you for your comments so far. They validate my suspicions.
> The procedures for checking index fragmentation and what-not can be
> very tedious. This is something I've traditionally avoided except in
> serious cases, because of the tedium. I'd be more inclined to dive in
> if there are tools that help speed up the discovery of problem spots.
> Have any of you used any tools to help speed up the research or to
> even automate the discovery of problemmatic indexes? Please share or
> link to your experiences if you are willing to share. I would love to
> learn from you as it will make my job easier.
> Sincere thanks,
> Osoalge
http://www.realsqlguy.com/bin/view/RealSQLGuy/DefraggingIndexes
Is it customary to reindex every night?
more production issues as I'm working in more complex businesses now.
One of the systems that we recently put into production is being
maintained by a non-DBA type whom I had a recent chat with. He told me
that they've found that the performance of the system seems to degrade
over a week as queries seem to take longer to execute as the week goes
on. So to combat the performance loss, he scheduled nightly reindexing
of the database.
Nightly reindexing of a database seems okay when you have the luxury
of not being a 24x7 business use application. However, I wouldn't have
ordinarily expected such harsh degredation over a weeks time period
(40 sec delays per query issued in some cases). This is a database
that is relatively more insert/update than select/report. I'm just
curious as to what your experiences have been? Have you found cases
where you've run indexing every night? If so why? If not, do you have
any opinions on what I should take a look at to investigate the
performance decrease?
Thanks in advance,
OsolageHi
"Osolage" wrote:
> I've been doing this DBA thing for a while. I'm having to deal with
> more production issues as I'm working in more complex businesses now.
> One of the systems that we recently put into production is being
> maintained by a non-DBA type whom I had a recent chat with. He told me
> that they've found that the performance of the system seems to degrade
> over a week as queries seem to take longer to execute as the week goes
> on. So to combat the performance loss, he scheduled nightly reindexing
> of the database.
> Nightly reindexing of a database seems okay when you have the luxury
> of not being a 24x7 business use application. However, I wouldn't have
> ordinarily expected such harsh degredation over a weeks time period
> (40 sec delays per query issued in some cases). This is a database
> that is relatively more insert/update than select/report. I'm just
> curious as to what your experiences have been? Have you found cases
> where you've run indexing every night? If so why? If not, do you have
> any opinions on what I should take a look at to investigate the
> performance decrease?
> Thanks in advance,
> Osolage
>
The amount of degredation is depending on the amount of change that the data
undergoes, therefore if there are a high number of transaction on the
database you may need to re-index more often. This can be made worse by
having poorly thought out fill factors or possibly even poor programming or
datatype selection.
Look at outputing what DBCC SHOWCONTIG gives before you re-index. You may
want to try and follow something similar to the example on the DBCC
SHOWCONTIG topic in books online which will only re-index when the
fragmentation gets above a certain level.
Also watch out for database shrinking (either auto or manual) which can also
cause fragmentation.
John|||Yes, I've seen this.
Generally, there was some sloppy code and design, such that the
database ran well as long as it was squeezed into available RAM, but
with even a little fragmentation the missing indexes and bad plans
caused an exponential degradation in performance.
There was initially a lot of inserting to tables with (nonsequential)
GUID clustered PKs, after that was changed to simple identity int's
much of the problem went away.
So, it was split between some sloppy code, and some scalability issues
that called for specific redesigns.
Some of these problems can be a real pain to diagnose, when they only
occur on the production box, with full-scale data, and different
critical points because of a different processor count and different
RAM layout than any dev environments.
J.
On 29 Jan 2007 22:15:25 -0800, "Osolage" <osolage@.gmail.com> wrote:
>I've been doing this DBA thing for a while. I'm having to deal with
>more production issues as I'm working in more complex businesses now.
>One of the systems that we recently put into production is being
>maintained by a non-DBA type whom I had a recent chat with. He told me
>that they've found that the performance of the system seems to degrade
>over a week as queries seem to take longer to execute as the week goes
>on. So to combat the performance loss, he scheduled nightly reindexing
>of the database.
>Nightly reindexing of a database seems okay when you have the luxury
>of not being a 24x7 business use application. However, I wouldn't have
>ordinarily expected such harsh degredation over a weeks time period
>(40 sec delays per query issued in some cases). This is a database
>that is relatively more insert/update than select/report. I'm just
>curious as to what your experiences have been? Have you found cases
>where you've run indexing every night? If so why? If not, do you have
>any opinions on what I should take a look at to investigate the
>performance decrease?
>Thanks in advance,
>Osolage|||Osolage wrote:
> I've been doing this DBA thing for a while. I'm having to deal with
> more production issues as I'm working in more complex businesses now.
> One of the systems that we recently put into production is being
> maintained by a non-DBA type whom I had a recent chat with. He told me
> that they've found that the performance of the system seems to degrade
> over a week as queries seem to take longer to execute as the week goes
> on. So to combat the performance loss, he scheduled nightly reindexing
> of the database.
> Nightly reindexing of a database seems okay when you have the luxury
> of not being a 24x7 business use application. However, I wouldn't have
> ordinarily expected such harsh degredation over a weeks time period
> (40 sec delays per query issued in some cases). This is a database
> that is relatively more insert/update than select/report. I'm just
> curious as to what your experiences have been? Have you found cases
> where you've run indexing every night? If so why? If not, do you have
> any opinions on what I should take a look at to investigate the
> performance decrease?
> Thanks in advance,
> Osolage
>
Depends on how the indexes are defined, how many inserts/updates across
index keys are occurring, etc. Also, as John mentioned, make sure
you're not shrinking the database - that will effectively "undo" any
reindexing that you've done.
Rather than rebuild EVERY index, consider rebuilding only those that are
fragmented. Here's a script to get you started. It needs a couple of
tweaks that I haven't gotten around to making, in particular it needs to
exclude index ID = 255, but it should get you started.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||You can look at Reorganize indexes and Reindex only highly fragmented
indexes.
BOL has good Example for it.
On Jan 30, 3:43 pm, JXStern <JXSternChange...@.gte.net> wrote:
> Yes, I've seen this.
> Generally, there was some sloppy code and design, such that the
> database ran well as long as it was squeezed into available RAM, but
> with even a little fragmentation the missing indexes and bad plans
> caused an exponential degradation in performance.
> There was initially a lot of inserting to tables with (nonsequential)
> GUID clustered PKs, after that was changed to simple identity int's
> much of the problem went away.
> So, it was split between some sloppy code, and some scalability issues
> that called for specific redesigns.
> Some of these problems can be a real pain to diagnose, when they only
> occur on the production box, with full-scale data, and different
> critical points because of a different processor count and different
> RAM layout than any dev environments.
> J.
> On 29 Jan 2007 22:15:25 -0800, "Osolage" <osol...@.gmail.com> wrote:
>
>
>
>
> - Show quoted text -|||Hi, everyone,
I thank you for your comments so far. They validate my suspicions.
The procedures for checking index fragmentation and what-not can be
very tedious. This is something I've traditionally avoided except in
serious cases, because of the tedium. I'd be more inclined to dive in
if there are tools that help speed up the discovery of problem spots.
Have any of you used any tools to help speed up the research or to
even automate the discovery of problemmatic indexes? Please share or
link to your experiences if you are willing to share. I would love to
learn from you as it will make my job easier.
Sincere thanks,
Osoalge|||On Feb 5, 4:38 pm, "Osolage" <osol...@.gmail.com> wrote:
> Hi, everyone,
> I thank you for your comments so far. They validate my suspicions.
> The procedures for checking index fragmentation and what-not can be
> very tedious. This is something I've traditionally avoided except in
> serious cases, because of the tedium. I'd be more inclined to dive in
> if there are tools that help speed up the discovery of problem spots.
> Have any of you used any tools to help speed up the research or to
> even automate the discovery of problemmatic indexes? Please share or
> link to your experiences if you are willing to share. I would love to
> learn from you as it will make my job easier.
> Sincere thanks,
> Osoalge
http://www.realsqlguy.com/bin/view/...fraggingIndexes
Is it customary to reindex every night?
more production issues as I'm working in more complex businesses now.
One of the systems that we recently put into production is being
maintained by a non-DBA type whom I had a recent chat with. He told me
that they've found that the performance of the system seems to degrade
over a week as queries seem to take longer to execute as the week goes
on. So to combat the performance loss, he scheduled nightly reindexing
of the database.
Nightly reindexing of a database seems okay when you have the luxury
of not being a 24x7 business use application. However, I wouldn't have
ordinarily expected such harsh degredation over a weeks time period
(40 sec delays per query issued in some cases). This is a database
that is relatively more insert/update than select/report. I'm just
curious as to what your experiences have been? Have you found cases
where you've run indexing every night? If so why? If not, do you have
any opinions on what I should take a look at to investigate the
performance decrease?
Thanks in advance,
OsolageHi
"Osolage" wrote:
> I've been doing this DBA thing for a while. I'm having to deal with
> more production issues as I'm working in more complex businesses now.
> One of the systems that we recently put into production is being
> maintained by a non-DBA type whom I had a recent chat with. He told me
> that they've found that the performance of the system seems to degrade
> over a week as queries seem to take longer to execute as the week goes
> on. So to combat the performance loss, he scheduled nightly reindexing
> of the database.
> Nightly reindexing of a database seems okay when you have the luxury
> of not being a 24x7 business use application. However, I wouldn't have
> ordinarily expected such harsh degredation over a weeks time period
> (40 sec delays per query issued in some cases). This is a database
> that is relatively more insert/update than select/report. I'm just
> curious as to what your experiences have been? Have you found cases
> where you've run indexing every night? If so why? If not, do you have
> any opinions on what I should take a look at to investigate the
> performance decrease?
> Thanks in advance,
> Osolage
>
The amount of degredation is depending on the amount of change that the data
undergoes, therefore if there are a high number of transaction on the
database you may need to re-index more often. This can be made worse by
having poorly thought out fill factors or possibly even poor programming or
datatype selection.
Look at outputing what DBCC SHOWCONTIG gives before you re-index. You may
want to try and follow something similar to the example on the DBCC
SHOWCONTIG topic in books online which will only re-index when the
fragmentation gets above a certain level.
Also watch out for database shrinking (either auto or manual) which can also
cause fragmentation.
John|||Yes, I've seen this.
Generally, there was some sloppy code and design, such that the
database ran well as long as it was squeezed into available RAM, but
with even a little fragmentation the missing indexes and bad plans
caused an exponential degradation in performance.
There was initially a lot of inserting to tables with (nonsequential)
GUID clustered PKs, after that was changed to simple identity int's
much of the problem went away.
So, it was split between some sloppy code, and some scalability issues
that called for specific redesigns.
Some of these problems can be a real pain to diagnose, when they only
occur on the production box, with full-scale data, and different
critical points because of a different processor count and different
RAM layout than any dev environments.
J.
On 29 Jan 2007 22:15:25 -0800, "Osolage" <osolage@.gmail.com> wrote:
>I've been doing this DBA thing for a while. I'm having to deal with
>more production issues as I'm working in more complex businesses now.
>One of the systems that we recently put into production is being
>maintained by a non-DBA type whom I had a recent chat with. He told me
>that they've found that the performance of the system seems to degrade
>over a week as queries seem to take longer to execute as the week goes
>on. So to combat the performance loss, he scheduled nightly reindexing
>of the database.
>Nightly reindexing of a database seems okay when you have the luxury
>of not being a 24x7 business use application. However, I wouldn't have
>ordinarily expected such harsh degredation over a weeks time period
>(40 sec delays per query issued in some cases). This is a database
>that is relatively more insert/update than select/report. I'm just
>curious as to what your experiences have been? Have you found cases
>where you've run indexing every night? If so why? If not, do you have
>any opinions on what I should take a look at to investigate the
>performance decrease?
>Thanks in advance,
>Osolage|||Osolage wrote:
> I've been doing this DBA thing for a while. I'm having to deal with
> more production issues as I'm working in more complex businesses now.
> One of the systems that we recently put into production is being
> maintained by a non-DBA type whom I had a recent chat with. He told me
> that they've found that the performance of the system seems to degrade
> over a week as queries seem to take longer to execute as the week goes
> on. So to combat the performance loss, he scheduled nightly reindexing
> of the database.
> Nightly reindexing of a database seems okay when you have the luxury
> of not being a 24x7 business use application. However, I wouldn't have
> ordinarily expected such harsh degredation over a weeks time period
> (40 sec delays per query issued in some cases). This is a database
> that is relatively more insert/update than select/report. I'm just
> curious as to what your experiences have been? Have you found cases
> where you've run indexing every night? If so why? If not, do you have
> any opinions on what I should take a look at to investigate the
> performance decrease?
> Thanks in advance,
> Osolage
>
Depends on how the indexes are defined, how many inserts/updates across
index keys are occurring, etc. Also, as John mentioned, make sure
you're not shrinking the database - that will effectively "undo" any
reindexing that you've done.
Rather than rebuild EVERY index, consider rebuilding only those that are
fragmented. Here's a script to get you started. It needs a couple of
tweaks that I haven't gotten around to making, in particular it needs to
exclude index ID = 255, but it should get you started.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||You can look at Reorganize indexes and Reindex only highly fragmented
indexes.
BOL has good Example for it.
On Jan 30, 3:43 pm, JXStern <JXSternChange...@.gte.net> wrote:
> Yes, I've seen this.
> Generally, there was some sloppy code and design, such that the
> database ran well as long as it was squeezed into available RAM, but
> with even a little fragmentation the missing indexes and bad plans
> caused an exponential degradation in performance.
> There was initially a lot of inserting to tables with (nonsequential)
> GUID clustered PKs, after that was changed to simple identity int's
> much of the problem went away.
> So, it was split between some sloppy code, and some scalability issues
> that called for specific redesigns.
> Some of these problems can be a real pain to diagnose, when they only
> occur on the production box, with full-scale data, and different
> critical points because of a different processor count and different
> RAM layout than any dev environments.
> J.
> On 29 Jan 2007 22:15:25 -0800, "Osolage" <osol...@.gmail.com> wrote:
>
> >I've been doing this DBA thing for a while. I'm having to deal with
> >more production issues as I'm working in more complex businesses now.
> >One of the systems that we recently put into production is being
> >maintained by a non-DBA type whom I had a recent chat with. He told me
> >that they've found that the performance of the system seems to degrade
> >over a week as queries seem to take longer to execute as the week goes
> >on. So to combat the performance loss, he scheduled nightly reindexing
> >of the database.
> >Nightly reindexing of a database seems okay when you have the luxury
> >of not being a 24x7 business use application. However, I wouldn't have
> >ordinarily expected such harsh degredation over a weeks time period
> >(40 sec delays per query issued in some cases). This is a database
> >that is relatively more insert/update than select/report. I'm just
> >curious as to what your experiences have been? Have you found cases
> >where you've run indexing every night? If so why? If not, do you have
> >any opinions on what I should take a look at to investigate the
> >performance decrease?
> >Thanks in advance,
> >Osolage- Hide quoted text -
> - Show quoted text -|||Hi, everyone,
I thank you for your comments so far. They validate my suspicions.
The procedures for checking index fragmentation and what-not can be
very tedious. This is something I've traditionally avoided except in
serious cases, because of the tedium. I'd be more inclined to dive in
if there are tools that help speed up the discovery of problem spots.
Have any of you used any tools to help speed up the research or to
even automate the discovery of problemmatic indexes? Please share or
link to your experiences if you are willing to share. I would love to
learn from you as it will make my job easier.
Sincere thanks,
Osoalge|||On Feb 5, 4:38 pm, "Osolage" <osol...@.gmail.com> wrote:
> Hi, everyone,
> I thank you for your comments so far. They validate my suspicions.
> The procedures for checking index fragmentation and what-not can be
> very tedious. This is something I've traditionally avoided except in
> serious cases, because of the tedium. I'd be more inclined to dive in
> if there are tools that help speed up the discovery of problem spots.
> Have any of you used any tools to help speed up the research or to
> even automate the discovery of problemmatic indexes? Please share or
> link to your experiences if you are willing to share. I would love to
> learn from you as it will make my job easier.
> Sincere thanks,
> Osoalge
http://www.realsqlguy.com/bin/view/RealSQLGuy/DefraggingIndexes
Friday, February 24, 2012
Is HierarchyUniqueNameStyle Enumeration Working?
Hi,
When I am performing a drillthrough on my cubes I discover the header of my drillthrough report of all column consist of [<DimensionUniqueName>].[<HierarchyName>]. I am trying to make the header of all columns to contain only [<HierarchyName>].
After reading http://msdn2.microsoft.com/en-us/library/microsoft.analysisservices.hierarchyuniquenamestyle.aspx, I set this property in my cube to ExcludeDimensionName, however, it does not solve remove the DimensionUniqueName from my drillthrough report.
Anyone has any idea how to remove DimensionUniqueName from the header of my drillthrough report?
I am having the same problem. hierarchyuniquenamestyle set to ExcludeDimensionNam doesn't work neither.Monday, February 20, 2012
IS ASP.Net 1.x Working together with SQL 2005?
Hi
Should ASP.Net 1.x work togheter with sql 2005 without problems? I have try to open a web project but I got the following error:
Cannot open database "crm" requested by the login. The login failed. Login failed for user 'crmuser'.
This crmuser is "promoted" to owner of the crm base, but still I got the problem.
I upgrade this web project to ASP.Net 2.0 and I don't have the login problems, that's why I'm wondring.
Hope someone can answear me on this question. Thanks!
Jan
SQL Server 2005 does not care what version is your application all you need is correct permissions and the correct connection string for 1.1, there are two permissions in SQL Server both are covered in the thread below and look up connections string for 1.1 in the product docs. Hope this helps.
http://forums.asp.net/thread/1492092.aspx
|||You solve my problems, thanks!!|||
lsoljf:
You solve my problems, thanks!!
I am glad I could help.