Is it possible to have a node that is running one default and one named
instance of SQL Server 2000, A second node that's running a default instance
of sql server 2000 and have both failover to a third node? Any thoughts,
suggestions, or answers would eb appreciated particular if your're currently
running this conifiguration.
You only get one default instance per cluster. You can use DNS to alias an
old server name to the new server name. Three node clusters are legal using
Windows Server 2003 Enterprise Edition and SQL Server 2000 Enterprise
Edition. You can control the failover path for each instance independantly.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Roger Newton" <RogerNewton@.discussions.microsoft.com> wrote in message
news:257A442B-6027-4C21-A29E-A51C05C65E8D@.microsoft.com...
> Is it possible to have a node that is running one default and one named
> instance of SQL Server 2000, A second node that's running a default
instance
> of sql server 2000 and have both failover to a third node? Any thoughts,
> suggestions, or answers would eb appreciated particular if your're
currently
> running this conifiguration.
|||Thanks for responding,
So it sounds like that if I'm running windows 2003, SQL server 2000
enterprise have 1 default instance and 1 named instance on node A and 1 named
instance on node B I will be able to failover all instances to a third node
(node C) for failover purposes. Sound right to you?
"Geoff N. Hiten" wrote:
> You only get one default instance per cluster. You can use DNS to alias an
> old server name to the new server name. Three node clusters are legal using
> Windows Server 2003 Enterprise Edition and SQL Server 2000 Enterprise
> Edition. You can control the failover path for each instance independantly.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Roger Newton" <RogerNewton@.discussions.microsoft.com> wrote in message
> news:257A442B-6027-4C21-A29E-A51C05C65E8D@.microsoft.com...
> instance
> currently
>
>
|||You could look at it that way. Instances (default or named) don't really
have an owner node in SQL 2000. All nodes are equal, except during installs
or upgrades. You can set a preferred host order and limit which hosts are
allowed to run which instances, but you have to do that yourself after
setup. I personally run a N+1 cluster where I have three instances and four
nodes. My only gripe is I have to manually reset the preferred node order
if anybody fails over so I don't overcommit memory on a single node.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Roger Newton" <RogerNewton@.discussions.microsoft.com> wrote in message
news:C43C55D9-65E7-40FE-A4A5-4A3DC76EE9E3@.microsoft.com...
> Thanks for responding,
> So it sounds like that if I'm running windows 2003, SQL server 2000
> enterprise have 1 default instance and 1 named instance on node A and 1
named
> instance on node B I will be able to failover all instances to a third
node[vbcol=seagreen]
> (node C) for failover purposes. Sound right to you?
> "Geoff N. Hiten" wrote:
an[vbcol=seagreen]
using[vbcol=seagreen]
independantly.[vbcol=seagreen]
named[vbcol=seagreen]
thoughts,[vbcol=seagreen]
|||thanks for the help
"Geoff N. Hiten" wrote:
> You could look at it that way. Instances (default or named) don't really
> have an owner node in SQL 2000. All nodes are equal, except during installs
> or upgrades. You can set a preferred host order and limit which hosts are
> allowed to run which instances, but you have to do that yourself after
> setup. I personally run a N+1 cluster where I have three instances and four
> nodes. My only gripe is I have to manually reset the preferred node order
> if anybody fails over so I don't overcommit memory on a single node.
> --
> Geoff N. Hiten
> Microsoft SQL Server MVP
> Senior Database Administrator
> Careerbuilder.com
> I support the Professional Association for SQL Server
> www.sqlpass.org
> "Roger Newton" <RogerNewton@.discussions.microsoft.com> wrote in message
> news:C43C55D9-65E7-40FE-A4A5-4A3DC76EE9E3@.microsoft.com...
> named
> node
> an
> using
> independantly.
> named
> thoughts,
>
>
Showing posts with label default. Show all posts
Showing posts with label default. Show all posts
Tuesday, March 20, 2012
Monday, March 19, 2012
2ND POST: Is there a way to insert a record using another as a tem
Hi
If you specify the column list then you insert values into those columns.
Missing columns will be set to NULL (if it is allowed) or a default value.
To update existing data use the UPDATE statement, you will only change the
values for columns specified in the SET clause. More information on the
INSERT and UPDATE statements can be found in Books Online.
Using stored procedure may help to remove any issues with different versions
as you will ship the correct procedure with the changes to the schema.
You can look at the INFORMATION_SCHEMA.columns view to find out what columns
a table has, although a different approach would be to only provide a
solution for the latest version and check they are on that version otherwise
force an upgrade.
John
"SA Development" wrote:
> Hi,
> I am currently inserting a record using:
> insert into TABLE(FIELD1,FIELD2) values ('%s',%d)
> But, the problem I have is that the table I am connecting to can either ha
ve
> 46 fields or 47 fields depending on its version. Is there a command that
> would allow me to use an existing record as a template and only specified
> the fields I want to change and then insert the new record?
> Something like:
> insert into TABLE(FIELD1) value ('%s') using template record where
> FIELD1='9999999' ?
> Thanks,
> SA Dev
>
>Thanks for the good ideas everyone, sorry my first post wasn't entirely
clear.
Lets say I have a table like this:
field1(key) field2 field3 field4 field5
9999 a b c d
What I was hoping to do is add a new record (field1=123 for example), but
use the 9999 as a template record so that its field values are inserted into
my new record EXCEPT for any that I override.
It sounds like the update command will let me update just the fields I want,
is there a way to tell SQL to copy record 9999 to record 123 and use all the
field values in record 9999 ?
Thanks,
Alan|||Hi David,
> INSERT INTO YourTable (col1, col2, col3, col4, col5)
> SELECT 123, col2, col3, col4, col5
> FROM YourTable
> WHERE col1 = 9999
Thank you -- that is exactly what I needed!
Thanks to everyone else who posted as well.
Have a great day,
Alan
If you specify the column list then you insert values into those columns.
Missing columns will be set to NULL (if it is allowed) or a default value.
To update existing data use the UPDATE statement, you will only change the
values for columns specified in the SET clause. More information on the
INSERT and UPDATE statements can be found in Books Online.
Using stored procedure may help to remove any issues with different versions
as you will ship the correct procedure with the changes to the schema.
You can look at the INFORMATION_SCHEMA.columns view to find out what columns
a table has, although a different approach would be to only provide a
solution for the latest version and check they are on that version otherwise
force an upgrade.
John
"SA Development" wrote:
> Hi,
> I am currently inserting a record using:
> insert into TABLE(FIELD1,FIELD2) values ('%s',%d)
> But, the problem I have is that the table I am connecting to can either ha
ve
> 46 fields or 47 fields depending on its version. Is there a command that
> would allow me to use an existing record as a template and only specified
> the fields I want to change and then insert the new record?
> Something like:
> insert into TABLE(FIELD1) value ('%s') using template record where
> FIELD1='9999999' ?
> Thanks,
> SA Dev
>
>Thanks for the good ideas everyone, sorry my first post wasn't entirely
clear.
Lets say I have a table like this:
field1(key) field2 field3 field4 field5
9999 a b c d
What I was hoping to do is add a new record (field1=123 for example), but
use the 9999 as a template record so that its field values are inserted into
my new record EXCEPT for any that I override.
It sounds like the update command will let me update just the fields I want,
is there a way to tell SQL to copy record 9999 to record 123 and use all the
field values in record 9999 ?
Thanks,
Alan|||Hi David,
> INSERT INTO YourTable (col1, col2, col3, col4, col5)
> SELECT 123, col2, col3, col4, col5
> FROM YourTable
> WHERE col1 = 9999
Thank you -- that is exactly what I needed!
Thanks to everyone else who posted as well.
Have a great day,
Alan
2nd Node does not come online
I have an "Active/Active" SQL 2000 cluster on Windows 2003 SP1. The first
node is the default instance and the second is a named instance. They are
both listenting on port 1433. When I fail the default instance over to the
2nd node, everything failsover and comes on line and I am able to connect and
query the data from both instances. I fail the node back over, again
everthing works.
When I fail the second node (named instance) over to the first node,
everthing fails over; however, the SQL Agent, Fulltext searching and the SQL
Server do not come on line. Any ideas on why this is happening? Thanks.
You can't have them both listening on port 1433. You can have one, say the
default, and the other DYNAMIC, which means SQL will randomly select a port.
When failed over it will attempt to acquire the same port as before, but not
always. The client rely on the Dynamic Discovery, UDP 1434, to detect which
port to use.
If you have these hard-coded, the named instance will fail whenever it fails
over to the node where the default instance has already acquired that port.
Consider it portetiquett, but no two TCP services can listen on the same
port on the same server. Sorry.
Sincerely,
Anthony Thomas
"MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
news:EC957BA9-76A8-42E4-AD8D-5F47354C149B@.microsoft.com...
> I have an "Active/Active" SQL 2000 cluster on Windows 2003 SP1. The first
> node is the default instance and the second is a named instance. They are
> both listenting on port 1433. When I fail the default instance over to the
> 2nd node, everything failsover and comes on line and I am able to connect
and
> query the data from both instances. I fail the node back over, again
> everthing works.
> When I fail the second node (named instance) over to the first node,
> everthing fails over; however, the SQL Agent, Fulltext searching and the
SQL
> Server do not come on line. Any ideas on why this is happening? Thanks.
node is the default instance and the second is a named instance. They are
both listenting on port 1433. When I fail the default instance over to the
2nd node, everything failsover and comes on line and I am able to connect and
query the data from both instances. I fail the node back over, again
everthing works.
When I fail the second node (named instance) over to the first node,
everthing fails over; however, the SQL Agent, Fulltext searching and the SQL
Server do not come on line. Any ideas on why this is happening? Thanks.
You can't have them both listening on port 1433. You can have one, say the
default, and the other DYNAMIC, which means SQL will randomly select a port.
When failed over it will attempt to acquire the same port as before, but not
always. The client rely on the Dynamic Discovery, UDP 1434, to detect which
port to use.
If you have these hard-coded, the named instance will fail whenever it fails
over to the node where the default instance has already acquired that port.
Consider it portetiquett, but no two TCP services can listen on the same
port on the same server. Sorry.
Sincerely,
Anthony Thomas
"MAGrimsley" <MAGrimsley@.discussions.microsoft.com> wrote in message
news:EC957BA9-76A8-42E4-AD8D-5F47354C149B@.microsoft.com...
> I have an "Active/Active" SQL 2000 cluster on Windows 2003 SP1. The first
> node is the default instance and the second is a named instance. They are
> both listenting on port 1433. When I fail the default instance over to the
> 2nd node, everything failsover and comes on line and I am able to connect
and
> query the data from both instances. I fail the node back over, again
> everthing works.
> When I fail the second node (named instance) over to the first node,
> everthing fails over; however, the SQL Agent, Fulltext searching and the
SQL
> Server do not come on line. Any ideas on why this is happening? Thanks.
Saturday, February 25, 2012
2005 SP2 Install Would complete
Hi,
I have a problem with my SQL Server 2005 instance after trying to install SP2.
My machine has a default instance of SQL server 2005, and 2 instances of SQL 2005 express.
I installed Express SP2 and this installed without a hitch.
Then I installed SP2 for SQL Server 2005. After the install, all the components had installed correctly except the Database Engine, which had a status of failed. I did not investigate why, I simply re-ran the install.
It failed again, so I investigated further and I found out it failed because it had not been able to start the service VSS Writer. I looked at the service, and found I had changed the user which gives the service rights to start. I changed this back to Local System so the service could start correctly.
I then re-ran the SP2 install. This time it failed in a different place. The reason this time was my user was not a valid user for my server. This is a first, because I logged onto the database using this user name minutes before running the install. The install must have deleted my user. Then I tried to login using the sa account only for my server telling me that the sa account has been disabled.
I now cannot log into my database at all, and am stuck. If I try to rerun the install it tells me it cannot connect to the server to perform the update because there is no user.
Please Help!
Are you able to proceed past the Authentication screen in the SP2 installation Wizard? If not what error are you seeing? Can you post your summary.txt file, which will be in %programFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
Thanks,
Peter Saddow
|||There was a failure during installation search up in this log file for this message:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'TSI\Sean'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<EndFunc Name='ComponentUpgrade' Return='18456' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Mon Feb 26 14:11:18 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='18456' GetLastError='0'>
MSI (s) (84:64) [14:11:19:083]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:083]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 14:11:19: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
Action ended 14:11:19: INSTALL. Return value 3.
--
Microsoft SQL Server 2005 Service Pack 2 Setup
--
Feature Selection
This setup program detected the following SQL Server 2005 features. Select the program
features that you would like to update. To see the details of a feature, click on the feature.
O Setup Support Files
X MSSQLSERVER
X Database Services
X Analysis Services Language ENU
X Reporting Services Platform x86
O SQLEXPRESS Edition DEVELOPER
O Database Services Status Upgraded
O Notification Services
O Integration Services
O SQL Server Native Client
O Client Components
O MSXML 6.0 Parser
O SQLXML4
O Backward Compatibility
O Microsoft SQL Server VSS Writer
|||After the previous screen I select next, then make sure Windows Authentication is selected then click next again.
-
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
After I click Ok & Back the Feature Selection screen shows details of:
Login Failed: HResult 0xE9, Level 16, State 1 Shared Memory Provider: No process is on the other end of the pipe. Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.
And it shows a status of:
Not Valid
|||I am getting the same issue.. can you help? When i am trying to install SP2
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
2005 SP2 Install Failed, and Now SQL Server is Unusable. - (SQL9_Hotfix_KB921896_sqlrun_sql.msp.
Hi,
I have a problem with my SQL Server 2005 instance after trying to install SP2.
My machine has a default instance of SQL server 2005, and 2 instances of SQL 2005 express.
I installed Express SP2 and this installed without a hitch.
Then I installed SP2 for SQL Server 2005. After the install, all the components had installed correctly except the Database Engine, which had a status of failed. I did not investigate why, I simply re-ran the install.
It failed again, so I investigated further and I found out it failed because it had not been able to start the service VSS Writer. I looked at the service, and found I had changed the user which gives the service rights to start. I changed this back to Local System so the service could start correctly.
I then re-ran the SP2 install. This time it failed in a different place. The reason this time was my user was not a valid user for my server. This is a first, because I logged onto the database using this user name minutes before running the install. The install must have deleted my user. Then I tried to login using the sa account only for my server telling me that the sa account has been disabled.
I now cannot log into my database at all, and am stuck. If I try to rerun the install it tells me it cannot connect to the server to perform the update because there is no user.
Please Help!
Are you able to proceed past the Authentication screen in the SP2 installation Wizard? If not what error are you seeing? Can you post your summary.txt file, which will be in %programFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
Thanks,
Peter Saddow
|||There was a failure during installation search up in this log file for this message:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'TSI\Sean'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<EndFunc Name='ComponentUpgrade' Return='18456' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Mon Feb 26 14:11:18 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='18456' GetLastError='0'>
MSI (s) (84:64) [14:11:19:083]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:083]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 14:11:19: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
Action ended 14:11:19: INSTALL. Return value 3.
--
Microsoft SQL Server 2005 Service Pack 2 Setup
--
Feature Selection
This setup program detected the following SQL Server 2005 features. Select the program
features that you would like to update. To see the details of a feature, click on the feature.
O Setup Support Files
X MSSQLSERVER
X Database Services
X Analysis Services Language ENU
X Reporting Services Platform x86
O SQLEXPRESS Edition DEVELOPER
O Database Services Status Upgraded
O Notification Services
O Integration Services
O SQL Server Native Client
O Client Components
O MSXML 6.0 Parser
O SQLXML4
O Backward Compatibility
O Microsoft SQL Server VSS Writer
|||After the previous screen I select next, then make sure Windows Authentication is selected then click next again.
-
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
After I click Ok & Back the Feature Selection screen shows details of:
Login Failed: HResult 0xE9, Level 16, State 1 Shared Memory Provider: No process is on the other end of the pipe. Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.
And it shows a status of:
Not Valid
|||I am getting the same issue.. can you help? When i am trying to install SP2
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
2005 SP2 Install Failed, and Now SQL Server is Unusable. - (SP2 Install Screen Shot)
Hi,
I have a problem with my SQL Server 2005 instance after trying to install SP2.
My machine has a default instance of SQL server 2005, and 2 instances of SQL 2005 express.
I installed Express SP2 and this installed without a hitch.
Then I installed SP2 for SQL Server 2005. After the install, all the components had installed correctly except the Database Engine, which had a status of failed. I did not investigate why, I simply re-ran the install.
It failed again, so I investigated further and I found out it failed because it had not been able to start the service VSS Writer. I looked at the service, and found I had changed the user which gives the service rights to start. I changed this back to Local System so the service could start correctly.
I then re-ran the SP2 install. This time it failed in a different place. The reason this time was my user was not a valid user for my server. This is a first, because I logged onto the database using this user name minutes before running the install. The install must have deleted my user. Then I tried to login using the sa account only for my server telling me that the sa account has been disabled.
I now cannot log into my database at all, and am stuck. If I try to rerun the install it tells me it cannot connect to the server to perform the update because there is no user.
Please Help!
Are you able to proceed past the Authentication screen in the SP2 installation Wizard? If not what error are you seeing? Can you post your summary.txt file, which will be in %programFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
Thanks,
Peter Saddow
|||There was a failure during installation search up in this log file for this message:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'TSI\Sean'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<EndFunc Name='ComponentUpgrade' Return='18456' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Mon Feb 26 14:11:18 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='18456' GetLastError='0'>
MSI (s) (84:64) [14:11:19:083]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:083]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 14:11:19: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
Action ended 14:11:19: INSTALL. Return value 3.
--
Microsoft SQL Server 2005 Service Pack 2 Setup
--
Feature Selection
This setup program detected the following SQL Server 2005 features. Select the program
features that you would like to update. To see the details of a feature, click on the feature.
O Setup Support Files
X MSSQLSERVER
X Database Services
X Analysis Services Language ENU
X Reporting Services Platform x86
O SQLEXPRESS Edition DEVELOPER
O Database Services Status Upgraded
O Notification Services
O Integration Services
O SQL Server Native Client
O Client Components
O MSXML 6.0 Parser
O SQLXML4
O Backward Compatibility
O Microsoft SQL Server VSS Writer
|||After the previous screen I select next, then make sure Windows Authentication is selected then click next again.
-
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
After I click Ok & Back the Feature Selection screen shows details of:
Login Failed: HResult 0xE9, Level 16, State 1 Shared Memory Provider: No process is on the other end of the pipe. Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.
And it shows a status of:
Not Valid
|||I am getting the same issue.. can you help? When i am trying to install SP2
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
2005 SP2 Install Failed, and Now SQL Server is Unusable.
Hi,
I have a problem with my SQL Server 2005 instance after trying to install SP2.
My machine has a default instance of SQL server 2005, and 2 instances of SQL 2005 express.
I installed Express SP2 and this installed without a hitch.
Then I installed SP2 for SQL Server 2005. After the install, all the components had installed correctly except the Database Engine, which had a status of failed. I did not investigate why, I simply re-ran the install.
It failed again, so I investigated further and I found out it failed because it had not been able to start the service VSS Writer. I looked at the service, and found I had changed the user which gives the service rights to start. I changed this back to Local System so the service could start correctly.
I then re-ran the SP2 install. This time it failed in a different place. The reason this time was my user was not a valid user for my server. This is a first, because I logged onto the database using this user name minutes before running the install. The install must have deleted my user. Then I tried to login using the sa account only for my server telling me that the sa account has been disabled.
I now cannot log into my database at all, and am stuck. If I try to rerun the install it tells me it cannot connect to the server to perform the update because there is no user.
Please Help!
Are you able to proceed past the Authentication screen in the SP2 installation Wizard? If not what error are you seeing? Can you post your summary.txt file, which will be in %programFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix
Thanks,
Peter Saddow
|||There was a failure during installation search up in this log file for this message:
SQL Server Setup could not connect to the database service for server configuration. The error was: [Microsoft][SQL Native Client][SQL Server]Login failed for user 'TSI\Sean'. Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
<EndFunc Name='ComponentUpgrade' Return='18456' GetLastError='0'>
PerfTime Stop: CommitSqlUpgrade : Mon Feb 26 14:11:18 2007
Gathering darwin properties for failure handling.
<EndFunc Name='LaunchFunction' Return='18456' GetLastError='0'>
MSI (s) (84:64) [14:11:19:083]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:083]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
MSI (s) (84:64) [14:11:19:099]: Transforming table InstallExecuteSequence.
MSI (s) (84:64) [14:11:19:099]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038
Action ended 14:11:19: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3.
Action ended 14:11:19: INSTALL. Return value 3.
--
Microsoft SQL Server 2005 Service Pack 2 Setup
--
Feature Selection
This setup program detected the following SQL Server 2005 features. Select the program
features that you would like to update. To see the details of a feature, click on the feature.
O Setup Support Files
X MSSQLSERVER
X Database Services
X Analysis Services Language ENU
X Reporting Services Platform x86
O SQLEXPRESS Edition DEVELOPER
O Database Services Status Upgraded
O Notification Services
O Integration Services
O SQL Server Native Client
O Client Components
O MSXML 6.0 Parser
O SQLXML4
O Backward Compatibility
O Microsoft SQL Server VSS Writer
|||After the previous screen I select next, then make sure Windows Authentication is selected then click next again.
-
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
After I click Ok & Back the Feature Selection screen shows details of:
Login Failed: HResult 0xE9, Level 16, State 1 Shared Memory Provider: No process is on the other end of the pipe. Sqlcmd: Error: Microsoft SQL Native Client : Communication link failure.
And it shows a status of:
Not Valid
|||I am getting the same issue.. can you help? When i am trying to install SP2
Your account information could not be verified.
Press Ok to return to Authentication Mode screen to determine the reason for failure.
For setup to verify your credentials the services must be startable, connectable, and you must be a SQL Server administrator.
Sunday, February 19, 2012
2005 Management Studio sa default 'arabic' language
When I open the properties for SA in 2005 Management Studio (MS) I see that the default language is Arabic. If I open 2000 Enterprise Manager for the same instance the language is English. Thanks.
As it appears you have found an issue with the management dialog or an underlying component. I have filed a bug for this so it can be followed up in a service pack (pending the team's decision to fix this).
In reality the default language is not Arabic but it is likely to be English (depending on your version of SQL Server 2005). So the dialog misrepresents this. So you don't need to learn yet another language ;-)
If I recall correctly, you can actually force it to English, and from there on it will display English as your default language. But that would be a workaround...
|||
Thanks. It seems to be more prevalent when SA has master as the default database.
2005 Management Studio sa default 'arabic' language
When I open the properties for SA in 2005 Management Studio (MS) I see that the default language is Arabic. If I open 2000 Enterprise Manager for the same instance the language is English. Thanks.
As it appears you have found an issue with the management dialog or an underlying component. I have filed a bug for this so it can be followed up in a service pack (pending the team's decision to fix this).
In reality the default language is not Arabic but it is likely to be English (depending on your version of SQL Server 2005). So the dialog misrepresents this. So you don't need to learn yet another language ;-)
If I recall correctly, you can actually force it to English, and from there on it will display English as your default language. But that would be a workaround...
|||
Thanks. It seems to be more prevalent when SA has master as the default database.
Monday, February 13, 2012
2005 Failover Cluster SAN drives best practices
I have a MS SQL 2005 default installation on a Windows 2003 cluster. I
currently have two nodes and I am planning on adding more instances to
run on the other node.
First, I am not sure I have setup my existing default instance the best
way for my cluster. I currently only have one 'Physical Disk' in the
cluster group which is a LUN on our SAN. Both the data files and log
files are stored there. What is the best practice to move the logs onto
another spindle? Do I have to just create another LUN?
I am about to add a few more instances. Does each one need to have it's
own LUN?
There is a limited amount of drive letters that I can create. Is there
a way to share a LUN between instances? I seem to remember reading a
feature of 2005 that was related to this but, for the life of me, I
cannot find it again.
Any help would be appreciated!
Thank you
Karl> What is the best practice to move the logs onto
> another spindle? Do I have to just create another LUN?
You should at least put yout transaction log files on a separate LUN from
your data LUN. This doesn't guarantee that your data and log would be placed
on separate spindles inside SAN because both LUNs can be carved from the same
set of disks, but at least it gives you some separation.
> I am about to add a few more instances.
> Does each one need to have it's own LUN?
Each clustered instance will be implemented a separate cluster resource
group with its own disk resource(s). Since you can't have the same read/write
disk as two separate disk resources in different resource groups, each
clustered instance needs its own LUN.
> There is a limited amount of drive letters that I can create. Is there
> a way to share a LUN between instances?
You can't really share drive letters. But SQL2005 fully supports mounted
volumes in a cluster. These volumes don't have to be assigned separate drive
letters. As long as they are made disk resources, and are mounted under a
root drive letter, you can have multiple volumes in a resource group (or an
instance) with as few as one drive letter per instance.
Linchi
"Karl" wrote:
> I have a MS SQL 2005 default installation on a Windows 2003 cluster. I
> currently have two nodes and I am planning on adding more instances to
> run on the other node.
> First, I am not sure I have setup my existing default instance the best
> way for my cluster. I currently only have one 'Physical Disk' in the
> cluster group which is a LUN on our SAN. Both the data files and log
> files are stored there. What is the best practice to move the logs onto
> another spindle? Do I have to just create another LUN?
> I am about to add a few more instances. Does each one need to have it's
> own LUN?
> There is a limited amount of drive letters that I can create. Is there
> a way to share a LUN between instances? I seem to remember reading a
> feature of 2005 that was related to this but, for the life of me, I
> cannot find it again.
> Any help would be appreciated!
> Thank you
> Karl
>
currently have two nodes and I am planning on adding more instances to
run on the other node.
First, I am not sure I have setup my existing default instance the best
way for my cluster. I currently only have one 'Physical Disk' in the
cluster group which is a LUN on our SAN. Both the data files and log
files are stored there. What is the best practice to move the logs onto
another spindle? Do I have to just create another LUN?
I am about to add a few more instances. Does each one need to have it's
own LUN?
There is a limited amount of drive letters that I can create. Is there
a way to share a LUN between instances? I seem to remember reading a
feature of 2005 that was related to this but, for the life of me, I
cannot find it again.
Any help would be appreciated!
Thank you
Karl> What is the best practice to move the logs onto
> another spindle? Do I have to just create another LUN?
You should at least put yout transaction log files on a separate LUN from
your data LUN. This doesn't guarantee that your data and log would be placed
on separate spindles inside SAN because both LUNs can be carved from the same
set of disks, but at least it gives you some separation.
> I am about to add a few more instances.
> Does each one need to have it's own LUN?
Each clustered instance will be implemented a separate cluster resource
group with its own disk resource(s). Since you can't have the same read/write
disk as two separate disk resources in different resource groups, each
clustered instance needs its own LUN.
> There is a limited amount of drive letters that I can create. Is there
> a way to share a LUN between instances?
You can't really share drive letters. But SQL2005 fully supports mounted
volumes in a cluster. These volumes don't have to be assigned separate drive
letters. As long as they are made disk resources, and are mounted under a
root drive letter, you can have multiple volumes in a resource group (or an
instance) with as few as one drive letter per instance.
Linchi
"Karl" wrote:
> I have a MS SQL 2005 default installation on a Windows 2003 cluster. I
> currently have two nodes and I am planning on adding more instances to
> run on the other node.
> First, I am not sure I have setup my existing default instance the best
> way for my cluster. I currently only have one 'Physical Disk' in the
> cluster group which is a LUN on our SAN. Both the data files and log
> files are stored there. What is the best practice to move the logs onto
> another spindle? Do I have to just create another LUN?
> I am about to add a few more instances. Does each one need to have it's
> own LUN?
> There is a limited amount of drive letters that I can create. Is there
> a way to share a LUN between instances? I seem to remember reading a
> feature of 2005 that was related to this but, for the life of me, I
> cannot find it again.
> Any help would be appreciated!
> Thank you
> Karl
>
Saturday, February 11, 2012
2005 beta Backup problems
Hi there,
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 seconds
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
Nelson
Please re-post this on the beta newsgroups.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson Andr" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>
|||Where can I find it? I've searched the whole microsoft site and couldn't find
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
>
>
|||http://communities.microsoft.com/new...=sqlserver2005
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
[vbcol=seagreen]
> Where can I find it? I've searched the whole microsoft site and couldn't find
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 seconds
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
Nelson
Please re-post this on the beta newsgroups.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson Andr" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>
|||Where can I find it? I've searched the whole microsoft site and couldn't find
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
>
>
|||http://communities.microsoft.com/new...=sqlserver2005
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
[vbcol=seagreen]
> Where can I find it? I've searched the whole microsoft site and couldn't find
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
2005 beta Backup problems
Hi there,
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 seconds
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
NelsonPlease re-post this on the beta newsgroups.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>|||Where can I find it? I've searched the whole microsoft site and couldn't find
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> > Hi there,
> > I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> > scheduled to run everyday but it never runs, I've all the services
> > running.
> > When I choose to execute in the moment it says it had success after 5
> > seconds
> > but nothing happens really.
> > Is this a limitation of the beta release? Or am I doing something wrong?
> > I've another instance instaled in the same server (but with sql2000
> > version-default instance) and the maintenance plans work fine.
> > thanks in advance.
> > Nelson
> >
>
>|||http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
> Where can I find it? I've searched the whole microsoft site and couldn't find
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
> > Please re-post this on the beta newsgroups.
> >
> > --
> > Wayne Snyder MCDBA, SQL Server MVP
> > Mariner, Charlotte, NC
> > (Please respond only to the newsgroup.)
> >
> > I support the Professional Association for SQL Server ( PASS) and it's
> > community of SQL Professionals.
> > "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> > news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> > > Hi there,
> > > I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> > > scheduled to run everyday but it never runs, I've all the services
> > > running.
> > > When I choose to execute in the moment it says it had success after 5
> > > seconds
> > > but nothing happens really.
> > > Is this a limitation of the beta release? Or am I doing something wrong?
> > > I've another instance instaled in the same server (but with sql2000
> > > version-default instance) and the maintenance plans work fine.
> > > thanks in advance.
> > > Nelson
> > >
> >
> >
> >
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 seconds
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
NelsonPlease re-post this on the beta newsgroups.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>|||Where can I find it? I've searched the whole microsoft site and couldn't find
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> > Hi there,
> > I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> > scheduled to run everyday but it never runs, I've all the services
> > running.
> > When I choose to execute in the moment it says it had success after 5
> > seconds
> > but nothing happens really.
> > Is this a limitation of the beta release? Or am I doing something wrong?
> > I've another instance instaled in the same server (but with sql2000
> > version-default instance) and the maintenance plans work fine.
> > thanks in advance.
> > Nelson
> >
>
>|||http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
> Where can I find it? I've searched the whole microsoft site and couldn't find
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
> > Please re-post this on the beta newsgroups.
> >
> > --
> > Wayne Snyder MCDBA, SQL Server MVP
> > Mariner, Charlotte, NC
> > (Please respond only to the newsgroup.)
> >
> > I support the Professional Association for SQL Server ( PASS) and it's
> > community of SQL Professionals.
> > "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> > news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> > > Hi there,
> > > I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> > > scheduled to run everyday but it never runs, I've all the services
> > > running.
> > > When I choose to execute in the moment it says it had success after 5
> > > seconds
> > > but nothing happens really.
> > > Is this a limitation of the beta release? Or am I doing something wrong?
> > > I've another instance instaled in the same server (but with sql2000
> > > version-default instance) and the maintenance plans work fine.
> > > thanks in advance.
> > > Nelson
> > >
> >
> >
> >
2005 beta Backup problems
Hi there,
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 second
s
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
NelsonPlease re-post this on the beta newsgroups.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson Andr" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>|||Where can I find it? I've searched the whole microsoft site and couldn't fin
d
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
>
>|||http://communities.microsoft.com/ne...p=sqlserver2005
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
[vbcol=seagreen]
> Where can I find it? I've searched the whole microsoft site and couldn't f
ind
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
>
I've created a maintenance plan in SQL2005 bet 2 (not default instance)
scheduled to run everyday but it never runs, I've all the services running.
When I choose to execute in the moment it says it had success after 5 second
s
but nothing happens really.
Is this a limitation of the beta release? Or am I doing something wrong?
I've another instance instaled in the same server (but with sql2000
version-default instance) and the maintenance plans work fine.
thanks in advance.
NelsonPlease re-post this on the beta newsgroups.
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"Nelson Andr" <NelsonAndr@.discussions.microsoft.com> wrote in message
news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
> Hi there,
> I've created a maintenance plan in SQL2005 bet 2 (not default instance)
> scheduled to run everyday but it never runs, I've all the services
> running.
> When I choose to execute in the moment it says it had success after 5
> seconds
> but nothing happens really.
> Is this a limitation of the beta release? Or am I doing something wrong?
> I've another instance instaled in the same server (but with sql2000
> version-default instance) and the maintenance plans work fine.
> thanks in advance.
> Nelson
>|||Where can I find it? I've searched the whole microsoft site and couldn't fin
d
any reference to a sql2005 beta newsgroup
"Wayne Snyder" wrote:
> Please re-post this on the beta newsgroups.
> --
> Wayne Snyder MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> (Please respond only to the newsgroup.)
> I support the Professional Association for SQL Server ( PASS) and it's
> community of SQL Professionals.
> "Nelson André" <NelsonAndr@.discussions.microsoft.com> wrote in message
> news:E0B1B330-9D78-4704-8FDF-3A855A5DF64E@.microsoft.com...
>
>|||http://communities.microsoft.com/ne...p=sqlserver2005
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Nelson André" wrote:
[vbcol=seagreen]
> Where can I find it? I've searched the whole microsoft site and couldn't f
ind
> any reference to a sql2005 beta newsgroup
> "Wayne Snyder" wrote:
>
Subscribe to:
Posts (Atom)