PDF-Reporting with SQL2005 Reporting Services

Hi All,
in SQL Server Business Intelligence Development Studio the reporting output
(for SQL2005 Reporting Services) can for instance be chosen as pdf or excel.
choosing pdf as output, if the tables contain more data than one DIN-A-4
page can display the tables are continued on the next page. the table header
is fortunately also repeated on each new pdf-page.
however choosing excel as output, the whole output of one table is written
into one excel spreadsheet. even if the height of the table containing the
data is more than the height of DIN-A-4 then the table is not continued on
another spreadsheet. this leads to the unfortunate phenomenon that printing
the excel workbook (with tables higher than DIN-A-4) results in DIN-A-4
printouts in which the table header is unfortunately NOT repeated on each
new printout-page. (this is due to the fact that the tables in the
spreadsheets are highre than DIN-A-4.)
unfortunately in our case the generated pdf output can not used to be
printed, because for each report there have to made slight adjustments by
each user which cannot be processed within the reporting workflow.
hence we really need a solution to programmatically adjust the excel-output
provided by the SQL Server Business Intelligence Development Studio so that
within the excel-output the spreadsheets will have the same page breaks like
the pdf-pages within the pdf-output.
we are desperately looking for a solution for this issue. can anybody state
A) if it is either impossible or
B) if it would be possible and which steps would be involved to achieve this
aim?
thanks a lot in advance for your assistance!
best regards, janHi All,
doesn't anybody have an idea on how to generate Excel-Reportings with
SQL2005 Reporting Services (with tables in the spreadsheets that are higher
than DIN-A-4 printouts) which are printable?
Has anybody yet managed to generate Excel-Output and make this output
printable so that on each printed DIN-A-4-printout the table headers are
repeated and the tables have correct page breaks?
best regards, jan
"Jan" <no@.no.com> schrieb im Newsbeitrag
news:OEjOaBiGHHA.1264@.TK2MSFTNGP03.phx.gbl...
> Hi All,
> in SQL Server Business Intelligence Development Studio the reporting
> output (for SQL2005 Reporting Services) can for instance be chosen as pdf
> or excel.
> choosing pdf as output, if the tables contain more data than one DIN-A-4
> page can display the tables are continued on the next page. the table
> header is fortunately also repeated on each new pdf-page.
> however choosing excel as output, the whole output of one table is written
> into one excel spreadsheet. even if the height of the table containing the
> data is more than the height of DIN-A-4 then the table is not continued on
> another spreadsheet. this leads to the unfortunate phenomenon that
> printing the excel workbook (with tables higher than DIN-A-4) results in
> DIN-A-4 printouts in which the table header is unfortunately NOT repeated
> on each new printout-page. (this is due to the fact that the tables in the
> spreadsheets are highre than DIN-A-4.)
> unfortunately in our case the generated pdf output can not used to be
> printed, because for each report there have to made slight adjustments by
> each user which cannot be processed within the reporting workflow.
> hence we really need a solution to programmatically adjust the
> excel-output provided by the SQL Server Business Intelligence Development
> Studio so that within the excel-output the spreadsheets will have the same
> page breaks like the pdf-pages within the pdf-output.
> we are desperately looking for a solution for this issue. can anybody
> state
> A) if it is either impossible or
> B) if it would be possible and which steps would be involved to achieve
> this aim?
> thanks a lot in advance for your assistance!
> best regards, jan
>

pb fail over automatic with one instance alias with data mirroring

Hello,

I've got a question about failover with the database mirroring.

I have 3 servers, 2 with SQL 2005 and 1 with SQL Express as witness.

After getting some problems to install database mirroring with Windows authentification, i had to create an authentification by certificate.

All goes well but my problem is about my primary instance SQL alias.

The alias on the primary doesn't follow on the secondary when the primary is down.

I've searched on forums and in the internet SQL web sites, but i didn't find anything.

I create another alias on the secondary but i don't know how to modify it in T-SQL...

I would like to know if there's any solution to modify an SQL instance alias by transact-SQL? or if anyone has already install on its servers, a fail over automatic with one instance alias with data mirroring in T-SQL?

Thank you all for your help...

Aliases are written to the registry, so you must edit the registry. There are a number of undocumented extended stored procedures that can be used for editing the registry. However, they are undocumented which means that they are unsupported.

The procedures are in the master database and begin with xp_reg. You can read a description of some of them for SQL 2000 here: http://www.sql-server-performance.com/ac_extended_stored_procedures.asp

I do not know what, if any, changes have been made to these procedures in 2005, so be very careful if you use them.

|||

Ok thanks for this issue.

But if i modify the registry i had to reboot my server and like i want an high avaibility access to my database without clustering them, it's not the way i think i'll take.

In SQL 2000, the SQL alias server up in the WINS, but with 2005, is there anyone who know where this information go? and how to modify it? I tried to find informations in my database, but i don't find anything yet..

In forums SQL, there's nothing too...

Anyone have experiences about database mirroring with moving alias when the SQL role change?

Thanks for your help...

|||

At my work, we don't use .Net so we can't use the new support for ADO connection failover

we decided to use DNS Alias to mimic the feature so that it won't be instant failover for the entire application, but should be shorten to 30-60 mins downtime (just change DNS Alias from Server1 to Server2, use Alias name in all applications)

|||

We are using a federated model where each client has it's own version of the database. The application logs in to a central core database for authentication and then redirects to the client database. Some of the older modules of our web application is using .Net 1.0 which is not mirroring aware. But since the application first checks the central database before connecting to the client database, it seemed like handling failover for these older modules would be as simple as changing the ServerName in the Central database to point to the other server. Unfortunately, this only works for new users, not existing ones. The application is caching the connection information, and even if I log off and back on, it tries to send me to the previous server.

Until these portions of the application have been recoded, I have set up a job (runs every minute) on the mirror server that checks for principal instances running on itself. If it finds one and it is in the synched state, it fails it back over to the original principal server.

|||

Hello,

I've found my answer on this site

http://blogs.developpeur.org/christian/archive/2006/11/04/SQL-Server-_3A00_-Alias-de-serveurs.aspx

We can change the alias SQL Server 2005 directly in the registry.

Thanks for your answers..

sql

pb fail over automatic with one instance alias with data mirroring

Hello,

I've got a question about failover with the database mirroring.

I have 3 servers, 2 with SQL 2005 and 1 with SQL Express as witness.

After getting some problems to install database mirroring with Windows authentification, i had to create an authentification by certificate.

All goes well but my problem is about my primary instance SQL alias.

The alias on the primary doesn't follow on the secondary when the primary is down.

I've searched on forums and in the internet SQL web sites, but i didn't find anything.

I create another alias on the secondary but i don't know how to modify it in T-SQL...

I would like to know if there's any solution to modify an SQL instance alias by transact-SQL? or if anyone has already install on its servers, a fail over automatic with one instance alias with data mirroring in T-SQL?

Thank you all for your help...

Aliases are written to the registry, so you must edit the registry. There are a number of undocumented extended stored procedures that can be used for editing the registry. However, they are undocumented which means that they are unsupported.

The procedures are in the master database and begin with xp_reg. You can read a description of some of them for SQL 2000 here: http://www.sql-server-performance.com/ac_extended_stored_procedures.asp

I do not know what, if any, changes have been made to these procedures in 2005, so be very careful if you use them.

|||

Ok thanks for this issue.

But if i modify the registry i had to reboot my server and like i want an high avaibility access to my database without clustering them, it's not the way i think i'll take.

In SQL 2000, the SQL alias server up in the WINS, but with 2005, is there anyone who know where this information go? and how to modify it? I tried to find informations in my database, but i don't find anything yet..

In forums SQL, there's nothing too...

Anyone have experiences about database mirroring with moving alias when the SQL role change?

Thanks for your help...

|||

At my work, we don't use .Net so we can't use the new support for ADO connection failover

we decided to use DNS Alias to mimic the feature so that it won't be instant failover for the entire application, but should be shorten to 30-60 mins downtime (just change DNS Alias from Server1 to Server2, use Alias name in all applications)

|||

We are using a federated model where each client has it's own version of the database. The application logs in to a central core database for authentication and then redirects to the client database. Some of the older modules of our web application is using .Net 1.0 which is not mirroring aware. But since the application first checks the central database before connecting to the client database, it seemed like handling failover for these older modules would be as simple as changing the ServerName in the Central database to point to the other server. Unfortunately, this only works for new users, not existing ones. The application is caching the connection information, and even if I log off and back on, it tries to send me to the previous server.

Until these portions of the application have been recoded, I have set up a job (runs every minute) on the mirror server that checks for principal instances running on itself. If it finds one and it is in the synched state, it fails it back over to the original principal server.

|||

Hello,

I've found my answer on this site

http://blogs.developpeur.org/christian/archive/2006/11/04/SQL-Server-_3A00_-Alias-de-serveurs.aspx

We can change the alias SQL Server 2005 directly in the registry.

Thanks for your answers..

Path to exe

I'm trying to automate opening the firewall for an instance of SQL.
For a given instance of SQL how do I find the path to the executable ?I like to use Process Explorer from sysinternals (now acquired by MS). Just
mouse over the process name, and it'll show you the image path.
Now, if the instance is not running, this won't tell. But you can always
look into the registry under
HKLM\SYSTEM\CurrentControlSet\Services\M
SSQLServer\ImagePath for teh default
instance and HKLM\SYSTEM\CurrentControlSet\Services\M
SSQL$<instance
name>\ImagePath for a named instance.
Linchi
"Michael Tissington" wrote:

> I'm trying to automate opening the firewall for an instance of SQL.
> For a given instance of SQL how do I find the path to the executable ?
>
>|||Hello Michael,
As Linchi has suggested, you can use the registry to find the certain SQL
Server instance/service's image path. Actually, the following registry
paths are the ones of SQL Server services.
HKLM\SYSTEM\CurrentControlSet\Services\M
SSQLServer\ImagePath for teh
default
HKLM\SYSTEM\CurrentControlSet\Services\M
SSQL$<instance name>\ImagePath
Therefore, in your code, you can loop through all those services and
checkout those ones that match the SQL server instances.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

Path to exe

I'm trying to automate opening the firewall for an instance of SQL.
For a given instance of SQL how do I find the path to the executable ?
I like to use Process Explorer from sysinternals (now acquired by MS). Just
mouse over the process name, and it'll show you the image path.
Now, if the instance is not running, this won't tell. But you can always
look into the registry under
HKLM\SYSTEM\CurrentControlSet\Services\MSSQLServer \ImagePath for teh default
instance and HKLM\SYSTEM\CurrentControlSet\Services\MSSQL$<inst ance
name>\ImagePath for a named instance.
Linchi
"Michael Tissington" wrote:

> I'm trying to automate opening the firewall for an instance of SQL.
> For a given instance of SQL how do I find the path to the executable ?
>
>

Path to exe

I'm trying to automate opening the firewall for an instance of SQL.
For a given instance of SQL how do I find the path to the executable ?
I like to use Process Explorer from sysinternals (now acquired by MS). Just
mouse over the process name, and it'll show you the image path.
Now, if the instance is not running, this won't tell. But you can always
look into the registry under
HKLM\SYSTEM\CurrentControlSet\Services\MSSQLServer \ImagePath for teh default
instance and HKLM\SYSTEM\CurrentControlSet\Services\MSSQL$<inst ance
name>\ImagePath for a named instance.
Linchi
"Michael Tissington" wrote:

> I'm trying to automate opening the firewall for an instance of SQL.
> For a given instance of SQL how do I find the path to the executable ?
>
>
|||Hello Michael,
As Linchi has suggested, you can use the registry to find the certain SQL
Server instance/service's image path. Actually, the following registry
paths are the ones of SQL Server services.
HKLM\SYSTEM\CurrentControlSet\Services\MSSQLServer \ImagePath for teh
default
HKLM\SYSTEM\CurrentControlSet\Services\MSSQL$<inst ance name>\ImagePath
Therefore, in your code, you can loop through all those services and
checkout those ones that match the SQL server instances.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

Patching WMSDE with SP4

Can anyone tell me whether WMSDE (which installs with WSUS) can be patched?
I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
message stating that SQL server is not installed.
Thanks in advance for your help.
Hi
You may want to print the exact error message, but any instance of SQL
Server should be patchable with the correct patch file.
John
"Buckeye" <Buckeye@.discussions.microsoft.com> wrote in message
news:94A93D9E-A8A8-481F-B1D8-12C9EA0E79E7@.microsoft.com...
> Can anyone tell me whether WMSDE (which installs with WSUS) can be
> patched?
> I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
> message stating that SQL server is not installed.
> Thanks in advance for your help.

Patching WMSDE with SP4

Can anyone tell me whether WMSDE (which installs with WSUS) can be patched?
I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
message stating that SQL server is not installed.
Thanks in advance for your help.Hi
You may want to print the exact error message, but any instance of SQL
Server should be patchable with the correct patch file.
John
"Buckeye" <Buckeye@.discussions.microsoft.com> wrote in message
news:94A93D9E-A8A8-481F-B1D8-12C9EA0E79E7@.microsoft.com...
> Can anyone tell me whether WMSDE (which installs with WSUS) can be
> patched?
> I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
> message stating that SQL server is not installed.
> Thanks in advance for your help.

Patching WMSDE with SP4

Can anyone tell me whether WMSDE (which installs with WSUS) can be patched?
I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
message stating that SQL server is not installed.
Thanks in advance for your help.Hi
You may want to print the exact error message, but any instance of SQL
Server should be patchable with the correct patch file.
John
"Buckeye" <Buckeye@.discussions.microsoft.com> wrote in message
news:94A93D9E-A8A8-481F-B1D8-12C9EA0E79E7@.microsoft.com...
> Can anyone tell me whether WMSDE (which installs with WSUS) can be
> patched?
> I am trying to apply MSDE SP4 to the WSUS instance and it returns an error
> message stating that SQL server is not installed.
> Thanks in advance for your help.

Patch question re: SQL 7.0 SP4

I'm getting ready to apply SQL 7.0 SP4 and the SQL Server instance is running on Win NT
4.0 SP6. According to http://support.microsoft.com/?id=327068, there is an
O/S patch that needs to be applied, per KB 258437. Fine and well, but then
I see in http:/
/support.microsoft.com/?id=821279 that this patch superseeds (sp?) the previ
ous SQL patch.
So, all that being said, do I still need to apply the O/S patch in KB 258437
? At what point to I apply the patch; before SP4, between SP4 and KB 821279
, or after KB 821279?
Better yet, how do I convince management / users / vendors to upgrade to Win
2K / SQL 2K? ;-)
TIA,
Mike
mstuart_nospam@.gates.comAll,
FYI, I spoke to some folks at Microsoft, and I was told to install SP4 then KB821279 (p
atch available at http://www.microsoft.com/downloads/...&displaylang=en) and that should take care of i
t.
Mike

Password is "too recent to change"

We have a "wizard" that deploys and configures a SQL 2005 instance for our
application. Among other things, it resets the SA password to a strong
password that is unknown to the client.
It works fine except now with installations on Vista. When the password is
set by the script it gets an error stating "Password Validation Failed. The
password for the user is too recent to change."
I've never had this problem before. We need to get around it but I see no
settings in SQL to adjust that. I also don't see any settings in Local
Policies for Vista that require a password exists for a certain amount of
time.
Anyone run into this yet and/or have a suggestion to solve it?
--
MazThe password policy that generates this message is called Minimum password
age - x days - you cannot change the password within x days from last
change. The default value on Vista probably differs from the one on your
previous OS.
Thanks
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
news:A921C953-A780-4C94-9497-94993579BB31@.microsoft.com...
> We have a "wizard" that deploys and configures a SQL 2005 instance for our
> application. Among other things, it resets the SA password to a strong
> password that is unknown to the client.
> It works fine except now with installations on Vista. When the password
> is
> set by the script it gets an error stating "Password Validation Failed.
> The
> password for the user is too recent to change."
> I've never had this problem before. We need to get around it but I see no
> settings in SQL to adjust that. I also don't see any settings in Local
> Policies for Vista that require a password exists for a certain amount of
> time.
> Anyone run into this yet and/or have a suggestion to solve it?
> --
> Maz|||I agree with that assessment. The question, unfortunately, still stands; ho
w
do we change it? More specifically, how do we change it programatically?
These are turn key setups. The customer will have no expertise in this
matter. We need to do this from our application wizard.
Since these are policy settings, I'm concerned it cannot be changed through
any software interface. Also, this is a SQL Server login and password not a
Windows password. Not sure why SQL is enforcing that OS rule.
Regardless, here's the dilema. Our wizard initially installs SQL Server
with a generic SA password using a command line install. After that step
completes, the password and other security settings are altered and this
instance is taken over by the applications setup wizard. We do a two step
process because sometimes there are problems getting SQL installed and manua
l
intervention is required. It is good to have the option of giving someone
the "install" SA password without needing to reveal the final operational SA
password which is a secret and embedded in the app.
Does anyone know how to change this policy back to zero programatically OR
any thought on how to do this install without risking exposing the SA
password?
My gut feeling is we're screwed by another somewhat arbitrary change
implemented by MSFT without consideration of the impacts to it's software
partners. Someone prove me wrong please? I'd love to be able to appologize
for jumping to that conclusion.
Maz
"Laurentiu Cristofor [MSFT]" wrote:

> The password policy that generates this message is called Minimum password
> age - x days - you cannot change the password within x days from last
> change. The default value on Vista probably differs from the one on your
> previous OS.
> Thanks
> --
> Laurentiu Cristofor [MSFT]
> Software Development Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
> news:A921C953-A780-4C94-9497-94993579BB31@.microsoft.com...
>
>|||Hold on. Microsoft had to fix a lot of the default open security holes.
While that can cause problems, they also gave us the tools to deal with the
issue.
Run this T-SQL command
ALTER LOGIN <yourloginname> WITH CHECK_POLICY = OFF
and it will stop checking the OS or domain password policy for SQL Server.
I woud recommend setting it back on after making all the changes.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
news:912129B0-B3BC-4986-905B-2A6031EEA9DF@.microsoft.com...[vbcol=seagreen]
>I agree with that assessment. The question, unfortunately, still stands;
>how
> do we change it? More specifically, how do we change it programatically?
> These are turn key setups. The customer will have no expertise in this
> matter. We need to do this from our application wizard.
> Since these are policy settings, I'm concerned it cannot be changed
> through
> any software interface. Also, this is a SQL Server login and password not
> a
> Windows password. Not sure why SQL is enforcing that OS rule.
> Regardless, here's the dilema. Our wizard initially installs SQL Server
> with a generic SA password using a command line install. After that step
> completes, the password and other security settings are altered and this
> instance is taken over by the applications setup wizard. We do a two
> step
> process because sometimes there are problems getting SQL installed and
> manual
> intervention is required. It is good to have the option of giving someone
> the "install" SA password without needing to reveal the final operational
> SA
> password which is a secret and embedded in the app.
> Does anyone know how to change this policy back to zero programatically OR
> any thought on how to do this install without risking exposing the SA
> password?
> My gut feeling is we're screwed by another somewhat arbitrary change
> implemented by MSFT without consideration of the impacts to it's software
> partners. Someone prove me wrong please? I'd love to be able to
> appologize
> for jumping to that conclusion.
> --
> Maz
>
> "Laurentiu Cristofor [MSFT]" wrote:
>|||Thanks Geoff. You are correct and I happily appologize to MSFT for jumping
to conclusions
I looked into Check_Policy. It's a a new parm and isn't supported in the
older DMO (which is how this routine was written). However, it was easy to
modify the function using TSQL and it worked perfectly.
Thanks again for that help. Hope this helps someone else moving to Vista.
Maz
"Geoff N. Hiten" wrote:

> Hold on. Microsoft had to fix a lot of the default open security holes.
> While that can cause problems, they also gave us the tools to deal with th
e
> issue.
> Run this T-SQL command
> ALTER LOGIN <yourloginname> WITH CHECK_POLICY = OFF
> and it will stop checking the OS or domain password policy for SQL Server.
> I woud recommend setting it back on after making all the changes.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
> news:912129B0-B3BC-4986-905B-2A6031EEA9DF@.microsoft.com...
>|||Geoff,
Maybe you can help with this related issue.
The lockout policy is set at 3 attempts in some period of time. Do you know,
other than the CHECK_POLICY = OFF method, to change this setting and do you
know what the period of time that SQL2005 is using?
Thanks
Chris
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:ucQ%23J%234VHHA.4568@.TK2MSFTNGP02.phx.gbl...
> Hold on. Microsoft had to fix a lot of the default open security holes.
> While that can cause problems, they also gave us the tools to deal with
> the issue.
> Run this T-SQL command
> ALTER LOGIN <yourloginname> WITH CHECK_POLICY = OFF
> and it will stop checking the OS or domain password policy for SQL Server.
> I woud recommend setting it back on after making all the changes.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
> news:912129B0-B3BC-4986-905B-2A6031EEA9DF@.microsoft.com...
>|||The password policy is inherited from either the local machine policy or the
OU domain-level group pollicy. Setting CHECK_POLICY off and back on will
unlock the account.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:e0bSzibWHHA.4188@.TK2MSFTNGP06.phx.gbl...
> Geoff,
> Maybe you can help with this related issue.
> The lockout policy is set at 3 attempts in some period of time. Do you
> know, other than the CHECK_POLICY = OFF method, to change this setting and
> do you know what the period of time that SQL2005 is using?
> Thanks
> Chris
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:ucQ%23J%234VHHA.4568@.TK2MSFTNGP02.phx.gbl...
>|||There is an UNLOCK option in ALTER LOGIN for unlocking locked out logins.
See http://msdn2.microsoft.com/en-us/library/ms189828.aspx.
Thanks
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:OpDDDScWHHA.1036@.TK2MSFTNGP03.phx.gbl...
> The password policy is inherited from either the local machine policy or
> the OU domain-level group pollicy. Setting CHECK_POLICY off and back on
> will unlock the account.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
> news:e0bSzibWHHA.4188@.TK2MSFTNGP06.phx.gbl...
>|||Laurentiu,
Previous experience had shown that this did not seem to work. Feb 2007 BOL
seems to have more relevant information about any restrictions.
Chris
"Laurentiu Cristofor [MSFT]" <Laurentiu.Cristofor@.nospam.com> wrote in
message news:%23ZkBGcfWHHA.3332@.TK2MSFTNGP04.phx.gbl...
> There is an UNLOCK option in ALTER LOGIN for unlocking locked out logins.
> See http://msdn2.microsoft.com/en-us/library/ms189828.aspx.
> Thanks
> --
> Laurentiu Cristofor [MSFT]
> Software Development Engineer
> SQL Server Engine
> http://blogs.msdn.com/lcris/
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:OpDDDScWHHA.1036@.TK2MSFTNGP03.phx.gbl...
>|||If you are hitting the Windows 2003 issue mentioned in the BOL link below,
then installing the last Service Pack for Windows 2003 should address the
problem. If you are seeing some other problem with UNLOCK, let us know.
Thanks
Laurentiu Cristofor [MSFT]
Software Development Engineer
SQL Server Engine
http://blogs.msdn.com/lcris/
This posting is provided "AS IS" with no warranties, and confers no rights.
"Chris Wood" <anonymous@.discussions.microsoft.com> wrote in message
news:%237A8lOoWHHA.4636@.TK2MSFTNGP02.phx.gbl...
> Laurentiu,
> Previous experience had shown that this did not seem to work. Feb 2007 BOL
> seems to have more relevant information about any restrictions.
> Chris
> "Laurentiu Cristofor [MSFT]" <Laurentiu.Cristofor@.nospam.com> wrote in
> message news:%23ZkBGcfWHHA.3332@.TK2MSFTNGP04.phx.gbl...
>

Passive node starting the SQL Server services - services set to ma

Hello all,
I have a very bizarre situation with a single instance/two node/W2K3
cluster. The issue I am seeing is that the passive node is starting the sql
server services even though the resources are not owned by that node. The
restarts are occuring every five minutes. The system log shows the SYSTEM
account starting MSSQLSERVER. Then, 3 seconds later, I get a message stating
the service stopped. About 5-8 seconds later, I get a message that the
SQLSERVERAGENT could not be started because sqlservr.exe is not running. The
cluster log is not showing anything being started/stopped. The applicaiton
log is complaining about the errorlog being unavailable. However, this is
correct because the resources are not on this node.
The SQL Server services are set to manual on both nodes. Both nodes have
been rebooted in the past 24 hours due to EMC PowerPath upgrades. The only
thing that is a little bizare is that the SQL Server resource group and SQL
Server resource have the preferred owners/possible owners in reverse order.
IE (SQL Server resource group has NODE1/NODE2; SQL Server Resource has
NODE2/NODE1). Right now all resources are on NODE1.
Any ideas would be greatly appreciated.
Thanks in advance
Chris.
Manual start for services is correct for a cluster. The cluster should
control the services on each node. Look at the applicaiotn logs on both
nodes. Check the failover/failback settings. You may be seeing a failback
condition due to different preferred node settings.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Christopher" <Christopher@.discussions.microsoft.com> wrote in message
news:E5873D57-2A8F-4B7B-B76C-7146B8A629DD@.microsoft.com...
> Hello all,
> I have a very bizarre situation with a single instance/two node/W2K3
> cluster. The issue I am seeing is that the passive node is starting the
> sql
> server services even though the resources are not owned by that node. The
> restarts are occuring every five minutes. The system log shows the SYSTEM
> account starting MSSQLSERVER. Then, 3 seconds later, I get a message
> stating
> the service stopped. About 5-8 seconds later, I get a message that the
> SQLSERVERAGENT could not be started because sqlservr.exe is not running.
> The
> cluster log is not showing anything being started/stopped. The
> applicaiton
> log is complaining about the errorlog being unavailable. However, this is
> correct because the resources are not on this node.
> The SQL Server services are set to manual on both nodes. Both nodes have
> been rebooted in the past 24 hours due to EMC PowerPath upgrades. The
> only
> thing that is a little bizare is that the SQL Server resource group and
> SQL
> Server resource have the preferred owners/possible owners in reverse
> order.
> IE (SQL Server resource group has NODE1/NODE2; SQL Server Resource has
> NODE2/NODE1). Right now all resources are on NODE1.
> Any ideas would be greatly appreciated.
> Thanks in advance
> Chris.