authentication on SQL 2005

I have an installation program that during install was able to authenticate
to SQL 2000 and validate "sa" and password. But it won't do that on SQL
2005. The program installs directly on the same box as that the SQL runs. Is
there any reason why authentication should fail?
Comments Please,
Michael ValeCruzAre you getting an error back? Did you set an SA password when you
installed SQL2k5?|||No error other than invalid user name and password.
Yes the password is valid, I use it to connect with the SQL Server
Management Studio using SQL Server Authentication and the SA is set with
server role "sysadmin"
I am just wondering if there is something in SQL 2000 that is automatically
on that is not turned on in SQL 2005 for this authentication to take place.
"PSPDBA" <williambr@.state.pa.us> wrote in message
news:1147285864.526093.215500@.v46g2000cwv.googlegroups.com...
> Are you getting an error back? Did you set an SA password when you
> installed SQL2k5?
>|||You might want to check that the program isn't sending MachineName\sa
instead of sa. When connecting from the same machine, I can't think of
anything that needs to be turned on. Look through the Surface Area
Configuration Tool and see if theres something that stands out..|||I met install experience when I intalled first SQL Server 2005 and second
SQL Server 2000.
In this situation I think that SA direct to S2K5 by default
"PSPDBA"?? ??? ??:

> You might want to check that the program isn't sending MachineName\sa
> instead of sa. When connecting from the same machine, I can't think of
> anything that needs to be turned on. Look through the Surface Area
> Configuration Tool and see if theres something that stands out..
>

Authentication methode

Is it possble to change the way users are authenticated within a SQL Server
2005 installation? And if so ho can it be done? I want to go from a Windows
Authentication to Windows Authentication/SQL Server Athentication..
TIA,
Arjan.Hi ,
i think you want to change the suthentication of server from windows to
windows and SQL
you can change by accessing server property from SQL Server management studio
change the security mode as per required.
Amol Lembhe
"Arjan" wrote:
> Is it possble to change the way users are authenticated within a SQL Server
> 2005 installation? And if so ho can it be done? I want to go from a Windows
> Authentication to Windows Authentication/SQL Server Athentication..
> TIA,
> Arjan.
>
>sql

Authentication methode

Is it possble to change the way users are authenticated within a SQL Server
2005 installation? And if so ho can it be done? I want to go from a Windows
Authentication to Windows Authentication/SQL Server Athentication..
TIA,
Arjan.Hi ,
i think you want to change the suthentication of server from windows to
windows and SQL
you can change by accessing server property from SQL Server management studi
o
change the security mode as per required.
Amol Lembhe
"Arjan" wrote:

> Is it possble to change the way users are authenticated within a SQL Serve
r
> 2005 installation? And if so ho can it be done? I want to go from a Window
s
> Authentication to Windows Authentication/SQL Server Athentication..
> TIA,
> Arjan.
>
>

Attaching previous database to new installation

I have a Active/Passive cluster and have installed the SQL 2005.
What I would like to know, before I proceed with my configurations (since it
is my first time in a cluster environment) is whether I will need to attach
the database (lets call it DBX) to SQL Server on both the servers seperately,
or do i only have to attach the database DBX to SQL Server on the active
machine.
Like i said this is my first time so i want to be very sure before i proceed.
You don't attach the database to any node. Rather, you attach it to the SQL
Server instance regardless which node the instance may be running at the
time. In general, a SQL Server operation doesn't care where the SQL instance
is running.
Linchi
"iqv1" wrote:

> I have a Active/Passive cluster and have installed the SQL 2005.
> What I would like to know, before I proceed with my configurations (since it
> is my first time in a cluster environment) is whether I will need to attach
> the database (lets call it DBX) to SQL Server on both the servers seperately,
> or do i only have to attach the database DBX to SQL Server on the active
> machine.
> Like i said this is my first time so i want to be very sure before i proceed.
|||thanks for you advice Linchi... I will try that
"Linchi Shea" wrote:
[vbcol=seagreen]
> You don't attach the database to any node. Rather, you attach it to the SQL
> Server instance regardless which node the instance may be running at the
> time. In general, a SQL Server operation doesn't care where the SQL instance
> is running.
> Linchi
> "iqv1" wrote:
|||Keep in mind that SQL Server will only be active on one node at a time. The
disks will only be visible from this active node; so, that is where you must
place the database files.
Then, as Linchi stated, you must run the attach process through the SQL
Server instance, just like you would on a stand-alone system.
You connect to the SQL Server instance through the failover cluster server
name dedicated for SQL Server, not specific node names.
Sincerely,
Anthony Thomas

"iqv1" <iqv1@.discussions.microsoft.com> wrote in message
news:81F95D4E-ACAE-4C99-9144-A91D963A83BD@.microsoft.com...[vbcol=seagreen]
> thanks for you advice Linchi... I will try that
> "Linchi Shea" wrote:
SQL[vbcol=seagreen]
instance[vbcol=seagreen]
(since it[vbcol=seagreen]
attach[vbcol=seagreen]
seperately,[vbcol=seagreen]
active[vbcol=seagreen]
proceed.

Attaching a mdf to a SQL Express instance during installation

Hi,

Im working in a proyect where i need to attach a mdf database to the client's SQL express instance. How can i accomplish during installation and without getting the user involved.

Any help will be greatly appretiated

I've been trying the following procedure:

Server svr = new Server(@."(local)\SQLEXPRESS");

System.Collections.Specialized.StringCollection sc = new System.Collections.Specialized.StringCollection();

sc.Add("c:\\Tester.mdf");

svr.AttachDatabase("Tester", sc);

But im getting the followin Error :

Exception has been thrown by the target of an invocation.

Any ideas?

|||

Hi,

could you please post the whole error message you are getting ? The problem is probably that the install process is using an account which is not priviledged to either access the files or attaching a database. if you want to use a special account to connect to the server you should use one of the other constructors of the server objects, specifying a special user or a connection string. if you have any further problems, come back with the whole error messages please.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

Thanks for answering Jens,

Here is the whole error Im getting:

Exception has been thrown by the target of an invocation.
StackTrace:
at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Delegate.DynamicInvokeImpl(Object[] args)
at System.Windows.Forms.Control.InvokeMarshaledCallbackDo(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbackHelper(Object obj)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Forms.Control.InvokeMarshaledCallback(ThreadMethodEntry tme)
at System.Windows.Forms.Control.InvokeMarshaledCallbacks()
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at System.Windows.Forms.Form.ShowDialog()
at Casa.it.MainForm.MainForm_Load(Object sender, EventArgs e) in C:\CS_Proyects\Casa.it\Casa.it\MainForm.cs:line 50
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.SendMessage(HandleRef hWnd, Int32 msg, Int32 wParam, Int32 lParam)
at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
at System.Windows.Forms.Control.set_Visible(Boolean value)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at Casa.it.Program.Main() in C:\CS_Proyects\Casa.it\Casa.it\Program.cs:line 19
Source:
mscorlib

Hope it helps.

Attaching a .mdf/.ldf on SQL Server

Trying to attach a SQL Server 2000 database (.mdf with .ldf) onto a fresh
installation of SQL Server 2000.
I get the message :
"Error 602: Could not find row in sysindexes for database ID 7, object ID 1,
index ID 1, Run DBCC CHECKTABLE on sysindexes."
Is there any way to use those files? Unfortunately, I don't have any
backups. Does it matter?I'd put the DB back on the source, run the DBCC, fix what needs to be fixed,
and start over.
"Savvoulidis Iordanis" wrote:
> Trying to attach a SQL Server 2000 database (.mdf with .ldf) onto a fresh
> installation of SQL Server 2000.
> I get the message :
> "Error 602: Could not find row in sysindexes for database ID 7, object ID 1,
> index ID 1, Run DBCC CHECKTABLE on sysindexes."
> Is there any way to use those files? Unfortunately, I don't have any
> backups. Does it matter?
>|||> I get the message :
> "Error 602: Could not find row in sysindexes for database ID 7, object ID
> 1,
> index ID 1, Run DBCC CHECKTABLE on sysindexes."
You can get this error message when trying to attach a database from a
higher version of SQL Server to a lower version. For example, trying to
attach a database from SQL Server 2005 on an instance of SQL Server 2000.
Doesn't sound like this is your case, but I thought I'd mention it just in
case.
--
Gail Erickson [MS]
SQL Server Documentation Team
This posting is provided "AS IS" with no warranties, and confers no rights
Download the latest version of Books Online from
http://technet.microsoft.com/en-us/sqlserver/bb428874.aspx
"Savvoulidis Iordanis" <Savvoulidis Iordanis@.discussions.microsoft.com>
wrote in message news:9E95AAB1-9737-40F7-A940-896F40716630@.microsoft.com...
> Trying to attach a SQL Server 2000 database (.mdf with .ldf) onto a fresh
> installation of SQL Server 2000.
> I get the message :
> "Error 602: Could not find row in sysindexes for database ID 7, object ID
> 1,
> index ID 1, Run DBCC CHECKTABLE on sysindexes."
> Is there any way to use those files? Unfortunately, I don't have any
> backups. Does it matter?
>