Viewing 15 posts - 16 through 30 (of 31 total)
Why are you doing two validations against CUR_STAGE?
You have already validated that they are 'IN' those particular definitions.
I would get rid of the WHERE clause.
February 12, 2009 at 3:00 pm
Do you not want the character that you listed on the left of your sample?
I would assume that it is exporting "column","column","column"...
If that is the case where your unwanted character...
February 11, 2009 at 4:15 pm
Tim,
It was my understanding that the /3GB parm in the boot.ini was only needed for windows XP. If you are running your SQL Servers on Server 2003 or greater...
February 3, 2009 at 8:44 am
If the above suggestions dont work for you there are other methods listed by Microsoft. Each of these methods do require DT.
January 23, 2009 at 9:12 am
Have you tried...
PASSWORD = { password | @password_variable }
instead of
MEDIAPASSWORD = { mediapassword | @mediapassword_variable }
It may be a long shot but I am sure it wouldnt hurt...
January 14, 2009 at 9:48 am
http://support.microsoft.com/kb/934749
Before you install the service pack and hotfixes, pause the other nodes. To do this, follow these steps:
1. Fail over to the new node.
2. Pause other nodes.
3. Install the SQL...
December 31, 2008 at 11:21 am
Can you uninstall the default instance and leave the remaining named instances intact?
December 9, 2008 at 8:27 am
Microsoft also recommends that you have applied service pack 4 to your SQL 2000 instances before installing SQL 2005 on the same cluster.
This would also need to be done if...
November 28, 2008 at 12:28 pm
If the failover cluster is working properly a simple refresh of the end-users screen should be enough to establish a new database connection.
Since the end-users connection should be setup looking...
November 28, 2008 at 12:12 pm
-- Login: xxx
CREATE LOGIN [xxx] WITH PASSWORD = xxx HASHED, SID = xxx, DEFAULT_DATABASE = [xxx], CHECK_POLICY = OFF, CHECK_EXPIRATION = OFF
Edited with the 'xxx' for security.
November 28, 2008 at 9:40 am
The T-SQL that was generated by the sp_help_revlogin all the users had the following code:
CHECK_POLICY = OFF, CHECK_EXPIRATION = OFF
and after doing a couple of searches I found that the...
November 26, 2008 at 3:16 pm
It was a 2005 to 2005 transfer and yes they have the same sort order.
The errors were 'log in failed please see your system administrator', changing their passwords worked and...
November 25, 2008 at 3:45 pm
FYI...
First morning into production, none of the user passwords passed through. For the lack of a better word the pw's were corrupt. We had to have all our...
November 24, 2008 at 8:04 am
That will work great for me thank you very much for the link.
November 22, 2008 at 10:51 am
Here is a really good thread on the topic.
http://www.sqlservercentral.com/Forums/Topic558227-146-1.aspx
November 21, 2008 at 11:27 am
Viewing 15 posts - 16 through 30 (of 31 total)