Viewing 15 posts - 91 through 105 (of 332 total)
Yes, the /passive command-line-install workaround did solve the problem. That's what I referred to as "fun".
March 14, 2014 at 7:02 am
I recently encountered the exact same problem. I needed to connect to a remote 32-bit Oracle database from a new install of 64-bit MSSQL. I didn't have the 64-bit ODBC...
March 13, 2014 at 7:55 am
Likewise, I did not know about this option. I was surprised it works! But good to know. Thanks for the question.
March 13, 2014 at 7:28 am
Each Instance needs to have the service pack applied. I don't remember, if the Service Pack Installation allows you to choose more than one instance during setup. Some components are...
March 6, 2014 at 8:51 am
Small point - you've raised your post in the SQL Server 2008 forum!
Database Mirroring was brand new in 2005; in fact, it wasn't even ready for the RTM release.
I assume...
March 6, 2014 at 4:08 am
I think maybe you are confusing yourself with the terminology of "server" to mean the physical hardware, the operating system and the MSSQL Instance.
Maybe if you ran through your procedure...
March 5, 2014 at 2:57 am
Just in case you are not aware: each Instance will listen on a TCP port (either fixed or dynamic) for standard database connections.
Separate to this, you need to create...
March 3, 2014 at 5:23 am
Hi,
I don't think there is any restriction on running the Witness & Mirror on the same server (although it is not a recommended configuration).
Follow the guidance here:
"How to: Add a...
February 28, 2014 at 3:55 am
At least Sharepoint doesn't simply demand sysadmin access. It indicates the developers thought about the problem. But as you say, securityadmin is almost the same as sysadmin. So I guess...
February 26, 2014 at 3:43 am
Unfortunately, I've come across many applications which require "sa" access. Sometimes, alternative scripts are provided, which need to be run as a sysadmin, avoiding the requirement for the installer to...
February 24, 2014 at 9:32 am
Could also be a mis-match of 32-bit vs. 64-bit, OS vs. MSSQL, and the hardware architecture. I received a similar error message once, and the root cause was: I had...
February 19, 2014 at 7:38 am
Assuming the machine-name will change, then make sure you run sp_dropserver/sp_addserver (Step L in the linked article). Definitely a gotcha step.
I've never migrated an existing database server between domains; I...
February 17, 2014 at 9:41 am
Can you check the SQL Server Agent Proxy settings on both servers A and B?
http://technet.microsoft.com/en-us/library/ms190926.aspx
Another thought is to check the Windows local security policy, for "Log on as a batch...
February 14, 2014 at 2:35 am
When you run xp_cmdshell, it runs under the security context of the SQL Server Service Account (not the account you are logged on as). One exception is, if your account...
December 2, 2013 at 6:41 am
Thanks GilaMonster and Jonathan.
The update, at the end of the MSDN blog, explains exactly the behaviour I am experiencing. Thank you for the link.
I am still a little mystified as...
August 27, 2013 at 4:18 am
Viewing 15 posts - 91 through 105 (of 332 total)