Help Im a Noob - Updating a database entry.

Ok, so I work with a certain program which has a wide open back door into it's data tables. As a program administrator i can go into the actual program and change details of other users etc. However here's what i need to do...

A certain users security level needs to be reduced from administrator to a lower level. If i do that within the program it will automatically require that i change that users password, which i don't know.

The user is not to know that their access level has changed.

Backdooring the database through MSQuery and hunting online a little i found how to update information...

UPDATE User
SET Security = 4
WHERE UserID = 4

This works fine, however the users password is then scrambled, until an administrator edits their password for them.

The password itself is encrypted within the database.
Appearing something like "99171821E244877B4201003E0519EEA7"
It appears to be hexadecimal, but hey, i'm no system engineer. Strange thing is. that encryption represents the password "bill". When i execute the change on security level, the password "bill" becomes invalid, yet the encrypted string remains exactly the same.

What i need if at all possible is a how to... on forcing the database to not change the password field when the security level is updated. Any other suggestions would be most welcome. And of course plain english with syntax explanations would be nice as i am very much a junior, this has been my first SQL code execution, aside from queries.

Cheers,
OostersUnfortunately for you, this seems to be an application issue.

If it were a DBMS problem, then I would assume you are not using ORACLE RDBMS; such problems only occur in mediocre DBMS like SQL Server and others.
:eek:|||Application problems seem pretty indiscriminant about what engines they affect to me. If an app uses SQL, and that SQL breaks, it breaks for any database that implements SQL at the same level. If an app uses database engine specific code (Oracle, Microsoft, DB2, etc), then that app will probably only run on its target database engine, but that is a failure in the application, not the database.

I think that the problem that Oosters has found is that multiple columns within the users table are used to derive (actually decrypt) the password. It would appear that the application designers wanted to prevent exactly the kind of change that Oosters is trying to make.

-PatP|||Unfortunately for you, this seems to be an application issue.

Indeed.

If it were a DBMS problem, then I would assume you are not using ORACLE RDBMS; such problems only occur in mediocre DBMS like SQL Server and others.
:eek:

And yet you felt it was imperative to squeeze that into your post regardless.

Quality.

Would you pretty pretty please proceed to regal me with unsolicited opinions and stories about how linux cured your stepdad's brother's cousin's dogs' nephew's sister's case of terminal cancer, or perhaps the one about Microsoft releasing OS's laced with mind control algorhythms that only appear at a particular resolution and refresh rate?|||In the midst of these response all i basically understood, was that the application designers didn't want me to do it. Why couldn't they just stop me backdooring the application in the first place.

Meanwhile I think i know what's happening with the password. I think instead of the database automatically changing the password when i update the security level of a user, there may be another field to lock the password when i update security level, and this will only unlock when another password is offered. I can't even get around it by feeding the database it's own encryption string, which should force it to recognise a password change. I'm off to hunt for a password locking field.

I could destroy the integrity of the entire database at the touch of a button, but i can't change a single users security level.|||In the midst of these response all i basically understood, was that the application designers didn't want me to do it. Why couldn't they just stop me backdooring the application in the first place.

Because controlling access to your database server probably isn't their job. Who is going to keep the database running if everybody is completely locked out of it?|||One of the really fundamental elements of good security design is to limit the damage that can be done without detection. A fundamental way to achieve this is to require some form of intervention from one or more of the affected parties whenever a change is made. The example you've got is when a security level is changed, make that change require a password change.

This has little to do with the database. It is a fundamental requisite for good security management.

While I'm sure that it frustrates you, I see it as a good thing in the larger context because it makes an otherwise unannounced change visible to the affected party. While it might not be politically expedient, you shouldn't be able (from a systemic point of view) to take away (or grant) administrative privledges without the knowledge of the user.

-PatP|||Yes, In an ideal world, in an ideal database i shouldn't be able to change user security levels without their knowledge. This being said...

<RANT>
Considering the sensitivity of information as this is a financial database representing the business of the whole company, I shouldn't be permitted to backdoor and alter financial information, and yet as long as i make it balance, which can take a bit of figuring, the database security allows such changes.
</RANT>

No need to respond to this, thanks for the knowledge people.

regards,
Matt

HELP HELP!

Hi All,
How do bring back the database that says
databasename(recovering)?
Thanks,
TonyIf it is recovering it's best to leave it until it finishes. Is there any
indication that it is recovering, disk activity etc, or do you think it's
stuck..?
--
HTH
Ryan Waight, MCDBA, MCSE
"Tony" <tonymailbox2001@.yahoo.com> wrote in message
news:24cd901c38d27$f9c0f800$a601280a@.phx.gbl...
> Hi All,
> How do bring back the database that says
> databasename(recovering)?
> Thanks,
> Tony

help getting parameters back from a stored procedure

Hello everyone,

I've been trying to use a stored procedure to return the names of some temporary tables that i put in the tempdb table in SQL Server.

--I've been getting the following error in visual basic 6 when i try to call this:
run-time error '-2147217900 (80040e14)': syntax access violation

--This is the error you get when you try to just run the code in query analyzer:
[Microsoft][ODBC SQL Server Driver]Syntax error or access violation

--what code i was trying to use (in query analyzer):
{call EXEC CreateTempTables (@.RQSodfil = 'a', @.BulkRan = 'a', @.BulkFor = 'a', @.BulkJit = 'a', @.ID = '0', @.RQSodfilFlag = '1', @.BulkRanFlag = '0', @.BulkForFlag = '0', @.BulkJitFlag = '0', @.DeleteFlag = '0', @.ErrorNum = '0')}

--code that i was trying to use in vb 6:
Public Sub TemporaryTables( _
ByVal bytRQSodfilFlag As Byte, _
ByVal bytBulkRanFlag As Byte, _
ByVal bytBulkForFlag As Byte, _
ByVal bytBulkJitFlag As Byte, _
ByVal bytDeleteFlag As Byte, _
ByVal cnPlant As String)

Dim objConn As ADODB.Connection
Dim objCmd As ADODB.Command
Dim objRQSodfil As Parameter
Dim objBulkRan As Parameter
Dim objBulkFor As Parameter
Dim objBulkJit As Parameter
Dim objParamID As Parameter
Dim objRQSodfilFlag As Parameter
Dim objBulkRanFlag As Parameter
Dim objBulkForFlag As Parameter
Dim objBulkJitFlag As Parameter
Dim objDeleteFlag As Parameter
Dim objErrorNum As Parameter
Dim intErrorNum As Integer

' setup command variable
Set objCmd = New ADODB.Command
Set objConn = New ADODB.Connection
objConn.Open cnPlant
objCmd.CommandText = "EXEC CreateTempTables"
objCmd.CommandType = adCmdStoredProc
objCmd.ActiveConnection = objConn

' setup parameters
Set objRQSodfil = objCmd.CreateParameter("@.RQSodfil", adVarChar, adParamInputOutput, 20, "a")
objCmd.Parameters.Append objRQSodfil
Set objBulkRan = objCmd.CreateParameter("@.BulkRan", adVarChar, adParamInputOutput, 20, "a")
objCmd.Parameters.Append objBulkRan
Set objBulkFor = objCmd.CreateParameter("@.BulkFor", adVarChar, adParamInputOutput, 20, "a")
objCmd.Parameters.Append objBulkFor
Set objBulkJit = objCmd.CreateParameter("@.BulkJit", adVarChar, adParamInputOutput, 20, "a")
objCmd.Parameters.Append objBulkJit
Set objParamID = objCmd.CreateParameter("@.ID", adChar, adParamInputOutput, 2, 0)
objCmd.Parameters.Append objParamID
Set objRQSodfilFlag = objCmd.CreateParameter("@.RQSodfilFlag", adTinyInt, adParamInput, , bytRQSodfilFlag)
objCmd.Parameters.Append objRQSodfilFlag
Set objBulkRanFlag = objCmd.CreateParameter("@.BulkRanFlag", adTinyInt, adParamInput, , bytBulkRanFlag)
objCmd.Parameters.Append objBulkRanFlag
Set objBulkForFlag = objCmd.CreateParameter("@.BulkForFlag", adTinyInt, adParamInput, , bytBulkForFlag)
objCmd.Parameters.Append objBulkForFlag
Set objBulkJitFlag = objCmd.CreateParameter("@.BulkJitFlag", adTinyInt, adParamInput, , bytBulkJitFlag)
objCmd.Parameters.Append objBulkJitFlag
Set objDeleteFlag = objCmd.CreateParameter("@.DeleteFlag", adTinyInt, adParamInput, , bytDeleteFlag)
objCmd.Parameters.Append objDeleteFlag
Set objErrorNum = objCmd.CreateParameter("@.ErrorNum", adInteger, adParamInputOutput, , 0)
objCmd.Parameters.Append objErrorNum

' execute command
Set rsTableInfo = objCmd.Execute(, , adExecuteRecord)

' find returned parameters
gstrRQSodfilName = rsTableInfo.Fields("@.RQSodfil")
gstrBulkRanName = rsTableInfo.Fields("@.BulkRan")
gstrBulkForName = rsTableInfo.Fields("@.BulkFor")
gstrBulkJitName = rsTableInfo.Fields("@.BulkJit")
gstrID = rsTableInfo.Fields("@.ID")
intErrorNum = rsTableInfo.Fields("@.ErrorNum")

End Sub

any help would be appreciatedactually i just solved my own problem:

at the end of the stored procedure i selected the columns i wanted to return and that did it.

select @.RQSodfil,@.BulkRan,@.BulkFor,@.BulkJit,@.ID,@.ErrorNum

i also just did a regular sql statement where i called the EXEC command to run my stored procedure.

EXEC CreateTempTables @.RQSodfil = 'a', @.BulkRan = 'a', @.BulkFor = 'a', @.BulkJit = 'a', @.ID = '0', @.RQSodfilFlag = '1', @.BulkRanFlag = '0', @.BulkForFlag = '0', @.BulkJitFlag = '0', @.DeleteFlag = '0', @.ErrorNum = '0'

hopefully if someone else has the same problem i've had they can see what i did.

Help Getting Back a Suspect Database

I had a database grow from 15Mb to 15Gb last week while I
was out of town and the standard Backups and Trans Log
Backups and Shrink Maintenance Plans didnt keep its size
down.
Well anyways now the log file is 15gb and the data file
is 15gb and SQL Enterprise Manager now reports the
database as suspect and I cant back it up or shrink it to
try and bring it down to a manageable size. The valid
backups are over a week old is there any way to recover
this database? It says that there is insufficient space
on the disk to work with the database. I have 70 gig free
now but it is still down. Any advice would be
appreciated. Thank you.did you try sp_resetstatus?
"Jerod" <jlindblom@.axonom.com> wrote in message
news:4a3101c3e445$53838370$a401280a@.phx.gbl...

quote:

---

> I had a database grow from 15Mb to 15Gb last week while I
> was out of town and the standard Backups and Trans Log
> Backups and Shrink Maintenance Plans didnt keep its size
> down.
> Well anyways now the log file is 15gb and the data file
> is 15gb and SQL Enterprise Manager now reports the
> database as suspect and I cant back it up or shrink it to
> try and bring it down to a manageable size. The valid
> backups are over a week old is there any way to recover
> this database? It says that there is insufficient space
> on the disk to work with the database. I have 70 gig free
> now but it is still down. Any advice would be
> appreciated. Thank you.

---

|||Hi,
The below procedure is listed in on of the articles
published at SQLServerCentral.com by Brian Knight
A database can be marked for many reasons. Generally it
falls into the following conditions :
A database or log file is missing.
In SQL 6.5, a device may not be present or in 7.0/2000 a
file may not exist.
SQL Server may not have been able to restore the database
in ample time.
The database could be corrupt.
The database is being help by the operating system. This
could be a 3rd party backup software or defrag software.
I've had even a virus scanning software cause this once.
SQL Server does not have enough space to recover the
database on startup.
To fix this problem, perform the following functions:
Review the SQL Server and NT error logs to see if you can
find where the problem occured.
Start SQL Server in single user mode.
Go to your control panel and services.
Stop SQL Server
Add the -m switch in the parameters pane below.
Start SQL Server
Run sp_resetstatus with the @.dbname parameter. (ie :
sp_resetstatus @.dbname = "pubs")
Perform detailed DBCC checks (CHECKDB, CHECKALLOC, etc)
Run a few random queries to see if you experience any
problems.
If no problems occur, stop and start SQL Server and open
the database to production.
As an absolute last resort, you can place your database in
emergency mode. By placing it in this mode, you will be
allowed to copy data out of the database, even if the data
is corrupt. To place your database in emergency mode, use
the following command:
SP_CONFIGURE 'allow updates', 1
RECONFIGURE WITH OVERRIDE
GO
UPDATE master..sysdatabases set status = -32768 WHERE name
= 'pubs'
GO
SP_CONFIGURE 'allow updates', 0
RECONFIGURE WITH OVERRIDE
You can then BCP data out and place it into a different
database.
HTH
--
Regards
THIRUMAL REDDY MARAM
SysAdmin/SQLServerDBA

quote:

---

>--Original Message--
>did you try sp_resetstatus?
>
>"Jerod" <jlindblom@.axonom.com> wrote in message
>news:4a3101c3e445$53838370$a401280a@.phx.gbl...
I[QUOTE]
to[QUOTE]
free[QUOTE]
>
>.
>

---

sql

Help Getting Back a Suspect Database

I had a database grow from 15Mb to 15Gb last week while I
was out of town and the standard Backups and Trans Log
Backups and Shrink Maintenance Plans didnt keep its size
down.
Well anyways now the log file is 15gb and the data file
is 15gb and SQL Enterprise Manager now reports the
database as suspect and I cant back it up or shrink it to
try and bring it down to a manageable size. The valid
backups are over a week old is there any way to recover
this database? It says that there is insufficient space
on the disk to work with the database. I have 70 gig free
now but it is still down. Any advice would be
appreciated. Thank you.did you try sp_resetstatus?
"Jerod" <jlindblom@.axonom.com> wrote in message
news:4a3101c3e445$53838370$a401280a@.phx.gbl...
> I had a database grow from 15Mb to 15Gb last week while I
> was out of town and the standard Backups and Trans Log
> Backups and Shrink Maintenance Plans didnt keep its size
> down.
> Well anyways now the log file is 15gb and the data file
> is 15gb and SQL Enterprise Manager now reports the
> database as suspect and I cant back it up or shrink it to
> try and bring it down to a manageable size. The valid
> backups are over a week old is there any way to recover
> this database? It says that there is insufficient space
> on the disk to work with the database. I have 70 gig free
> now but it is still down. Any advice would be
> appreciated. Thank you.|||Hi,
The below procedure is listed in on of the articles
published at SQLServerCentral.com by Brian Knight
A database can be marked for many reasons. Generally it
falls into the following conditions :
A database or log file is missing.
In SQL 6.5, a device may not be present or in 7.0/2000 a
file may not exist.
SQL Server may not have been able to restore the database
in ample time.
The database could be corrupt.
The database is being help by the operating system. This
could be a 3rd party backup software or defrag software.
I've had even a virus scanning software cause this once.
SQL Server does not have enough space to recover the
database on startup.
To fix this problem, perform the following functions:
Review the SQL Server and NT error logs to see if you can
find where the problem occured.
Start SQL Server in single user mode.
Go to your control panel and services.
Stop SQL Server
Add the -m switch in the parameters pane below.
Start SQL Server
Run sp_resetstatus with the @.dbname parameter. (ie :
sp_resetstatus @.dbname = "pubs")
Perform detailed DBCC checks (CHECKDB, CHECKALLOC, etc)
Run a few random queries to see if you experience any
problems.
If no problems occur, stop and start SQL Server and open
the database to production.
As an absolute last resort, you can place your database in
emergency mode. By placing it in this mode, you will be
allowed to copy data out of the database, even if the data
is corrupt. To place your database in emergency mode, use
the following command:
SP_CONFIGURE 'allow updates', 1
RECONFIGURE WITH OVERRIDE
GO
UPDATE master..sysdatabases set status = -32768 WHERE name
= 'pubs'
GO
SP_CONFIGURE 'allow updates', 0
RECONFIGURE WITH OVERRIDE
You can then BCP data out and place it into a different
database.
HTH
--
Regards
THIRUMAL REDDY MARAM
SysAdmin/SQLServerDBA
>--Original Message--
>did you try sp_resetstatus?
>
>"Jerod" <jlindblom@.axonom.com> wrote in message
>news:4a3101c3e445$53838370$a401280a@.phx.gbl...
>> I had a database grow from 15Mb to 15Gb last week while
I
>> was out of town and the standard Backups and Trans Log
>> Backups and Shrink Maintenance Plans didnt keep its size
>> down.
>> Well anyways now the log file is 15gb and the data file
>> is 15gb and SQL Enterprise Manager now reports the
>> database as suspect and I cant back it up or shrink it
to
>> try and bring it down to a manageable size. The valid
>> backups are over a week old is there any way to recover
>> this database? It says that there is insufficient space
>> on the disk to work with the database. I have 70 gig
free
>> now but it is still down. Any advice would be
>> appreciated. Thank you.
>
>.
>

HELP cannot start sqlserver.....

Help
We changed the Administrator Password, and now I cannot start Sqlserver on one of my systems.
And no password I try will apparently bring it back online
What can I do to reset password etc.
What error are you getting? Is that the account used by the SQL Service? If
so, you'll have to update the password in the Services applet, for
MSSQLServer service.
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"sqlstopper" <sqlstopper@.discussions.microsoft.com> wrote in message
news:756D0E5C-4E50-4098-8D26-9DD5ABF1490F@.microsoft.com...
> Help
> We changed the Administrator Password, and now I cannot start Sqlserver on
one of my systems.
> And no password I try will apparently bring it back online
> What can I do to reset password etc.
|||The error I get is: Did not start due to logon failure.
Just where do I change the password?
regards
"Narayana Vyas Kondreddi" wrote:

> What error are you getting? Is that the account used by the SQL Service? If
> so, you'll have to update the password in the Services applet, for
> MSSQLServer service.
> --
> Vyas, MVP (SQL Server)
> http://vyaskn.tripod.com/
>
> "sqlstopper" <sqlstopper@.discussions.microsoft.com> wrote in message
> news:756D0E5C-4E50-4098-8D26-9DD5ABF1490F@.microsoft.com...
> one of my systems.
>
>
|||OK that did the trick!!!!
thank you very much
I just love you 'MVP (SQL Server)'-guys
Wonderfull Job
thx
"Narayana Vyas Kondreddi" wrote:

> What error are you getting? Is that the account used by the SQL Service? If
> so, you'll have to update the password in the Services applet, for
> MSSQLServer service.
> --
> Vyas, MVP (SQL Server)
> http://vyaskn.tripod.com/
>
> "sqlstopper" <sqlstopper@.discussions.microsoft.com> wrote in message
> news:756D0E5C-4E50-4098-8D26-9DD5ABF1490F@.microsoft.com...
> one of my systems.
>
>
|||You could change the password through Enterprise manager under Security >>
Logins, right click the logins and go into Properties and change, for SQL
Logins.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
|||Is this the sa password? Can you try logging on using a Windows NT account
taht has admin rights?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

HELP cannot start sqlserver.....

Help
We changed the Administrator Password, and now I cannot start Sqlserver on o
ne of my systems.
And no password I try will apparently bring it back online
What can I do to reset password etc.What error are you getting? Is that the account used by the SQL Service? If
so, you'll have to update the password in the Services applet, for
MSSQLServer service.
--
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
"sqlstopper" <sqlstopper@.discussions.microsoft.com> wrote in message
news:756D0E5C-4E50-4098-8D26-9DD5ABF1490F@.microsoft.com...
> Help
> We changed the Administrator Password, and now I cannot start Sqlserver on
one of my systems.
> And no password I try will apparently bring it back online
> What can I do to reset password etc.|||The error I get is: Did not start due to logon failure.
Just where do I change the password?
regards
"Narayana Vyas Kondreddi" wrote:

> What error are you getting? Is that the account used by the SQL Service? I
f
> so, you'll have to update the password in the Services applet, for
> MSSQLServer service.
> --
> Vyas, MVP (SQL Server)
> http://vyaskn.tripod.com/
>
> "sqlstopper" <sqlstopper@.discussions.microsoft.com> wrote in message
> news:756D0E5C-4E50-4098-8D26-9DD5ABF1490F@.microsoft.com...
> one of my systems.
>
>|||OK that did the trick!!!!
thank you very much
I just love you 'MVP (SQL Server)'-guys
Wonderfull Job
thx
"Narayana Vyas Kondreddi" wrote:

> What error are you getting? Is that the account used by the SQL Service? I
f
> so, you'll have to update the password in the Services applet, for
> MSSQLServer service.
> --
> Vyas, MVP (SQL Server)
> http://vyaskn.tripod.com/
>
> "sqlstopper" <sqlstopper@.discussions.microsoft.com> wrote in message
> news:756D0E5C-4E50-4098-8D26-9DD5ABF1490F@.microsoft.com...
> one of my systems.
>
>|||You could change the password through Enterprise manager under Security >>
Logins, right click the logins and go into Properties and change, for SQL
Logins.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||Is this the sa password? Can you try logging on using a Windows NT account
taht has admin rights?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.

HELP Access to sql server 2005 express connection FAILS UPDATE

Hi

I got an access 2002 application front end with a sql server 2005 express back end. Some of my clients are having some difficulties. After using the application for a while, some of the users are finding that the system just hangs up. It usually happens after the front end application has been running for about an hour (sometimes sooner and sometimes later). There are perhaps 1 to 5 concurrent users and I have checked to see if there are any firewalls stalling it (I think I check all of them)- Is there any way that SQL Server 2005 express could be caused to just stall- This even occurs with the odd laptop. All the appropriate protocols are enabled as well. These databses are not very large.

ANY HELP WOULD BE GREATLY APPRETIATED!!!

Thanks

Frank Srebot

Moved thread to the SQL Server Express forum.|||

hi Frank,

what do you mean by "just hangs up"? does it completely stalls requiring a reboot, or it's "sleeeping" for just a while and then restarts working "as expected" or the like?

to start, few things to consider..

SQLExpress sets the "autoclose" property of it's created databases to true, and this causes the dbs to be shut down when not in use, meaning that tyey will be closed if no active connection references them.. this involves a little overhead at next re-use as the dbs must be re-open, but I do not think this is your problem... anyway, the eventual related "problem" can be workaround modifying the relative database property via sp_dboption database's system stored procedure call...

"autoshrink" database property is even set to true, and this causes, at engine scheduled time frames, the eventual shrinking of the involved databases, so that when lots of insert/delete operations are performed (actually lots of deletes), the engine wakes up a thread to shrink (when necessary) the databases, requiring some time to execute..

if the autogrowth property of the database's datafiles and logfiles is set to true and the engine states new file space is required, the engine enlarges the files (when needed) and this will obviously involve some time as well...

other non SQL Server related issues includes OS's scheduled tasks requiring lots of CPU and/or I/O..

but it's hard to solve this way

regards

|||

Thanks for the great and quick response.

To clarify, sql server just hangs up meaning that the application displays an hourglass and eventually the sql connection is lost and an error message is given. I was doing some research and I was wondering if the problem could be in the connection pooling configuration- currently the setting are that pool connections are enabled by default in the ODBC config settings- the databases which I am dealing are quite small- would any one have any ideas perhaps along these lines?

Thanks

Frank srebot

|||

Hi

This is an update to my connection Problem with Access 2002 to SQL SERVER EXPRESS 2005.

We are having random disconnects on the client side with Access putting up a "Connection Failure" dialog box even when the user is actively entering records into the system. Have any of you ever encountered this situation? We have disabled all TCP offloading engine technology on the machine thinking this was causing a problem with SQL Server as well as changing network cards to a whole different brand. We've pretty much ruled out the physical network at this point because we have changed cables and moved to another port on a different switch to no avail.

Is there some timeout setting or connection pooling setting that I am unaware of at the SQL Server level that has a problem interacting with Windows Server 2003 or Windows XP? I have checked and double checked all of the server settings between the old machine and the new and they are identical.

I did read that the connection pooling may be stressed and the pool of connections are 'Leaking'. This might be due to a bad cable or connection, but thats all I have found out.

Any info would be greatly appreciated.

Thanks

Frank

HELP : How to back up a database on ms sql 2005 studio express

hi

Im using the free version of ms sql 2005 studio express. I can upload databases, edit them and check them etc.

how do I back them up on to my pc, I do not have the server with me, my ms database is hosted on namesco.co.uk hosting.

I know how to right click the database, click task and back up. But I dont know where to back it up?

Whenever I try to back up to somewhere on my c: drive it won't. I think it also only backs up on a .bak files. Which I don't have.

I've looked on the net and it says you need a seperate hard drive or tape drive for back. Do I need to add another hard drive to my pc, if yes what do I format it as. And also how do I get a .bak file?

Here is a screenshot of where I can get to:(you might have to copy and paste them in your browser, there bmp so are big images)

http://www.uktattoostudios.co.uk/images/ms1.bmp

http://www.uktattoostudios.co.uk/images/ms3.bmp

As you can see I dont have a .bak to choose so it comes up this. If I click ok and try and back it up, it says back up complete. However when I go in the folder there is no .bak file

I also read on the net that if there shared databases the hosts are the only ones who can back stuff up, I asked them and they said that I should be able to do it on ms sql studio express.

thanks

dave

Backup folder are relative to the server. So every drive / file dialogue you see during the backup is from the server not from the client.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

hi, ok thanks.

So is there no way users can back up there databases? Sounds a bit stupid really?

Also namesco said I should be able to back it up

|||YOu can, but you will have to transfer the backup somehome on the client computer if you want to have if there.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||In Management Studio, right click on the database name, select Tasks|Backup.|||

hi,

rongolini wrote:

In Management Studio, right click on the database name, select Tasks|Backup.

this sounds difficult, if the server resides in a remote hosting company... as Jens anlready pointed out, the backup still resides on the remote machine and you have the hoster to provide a way (say a remote folder you can access over FTP) to bring it home...

regards

HELP : How to back up a database on ms sql 2005 studio express

hi

Im using the free version of ms sql 2005 studio express. I can upload databases, edit them and check them etc.

how do I back them up on to my pc, I do not have the server with me, my ms database is hosted on namesco.co.uk hosting.

I know how to right click the database, click task and back up. But I dont know where to back it up?

Whenever I try to back up to somewhere on my c: drive it won't. I think it also only backs up on a .bak files. Which I don't have.

I've looked on the net and it says you need a seperate hard drive or tape drive for back. Do I need to add another hard drive to my pc, if yes what do I format it as. And also how do I get a .bak file?

Here is a screenshot of where I can get to:(you might have to copy and paste them in your browser, there bmp so are big images)

http://www.uktattoostudios.co.uk/images/ms1.bmp

http://www.uktattoostudios.co.uk/images/ms3.bmp

As you can see I dont have a .bak to choose so it comes up this. If I click ok and try and back it up, it says back up complete. However when I go in the folder there is no .bak file

I also read on the net that if there shared databases the hosts are the only ones who can back stuff up, I asked them and they said that I should be able to do it on ms sql studio express.

thanks

dave

Backup folder are relative to the server. So every drive / file dialogue you see during the backup is from the server not from the client.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

hi, ok thanks.

So is there no way users can back up there databases? Sounds a bit stupid really?

Also namesco said I should be able to back it up

|||YOu can, but you will have to transfer the backup somehome on the client computer if you want to have if there.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||In Management Studio, right click on the database name, select Tasks|Backup.|||

hi,

rongolini wrote:

In Management Studio, right click on the database name, select Tasks|Backup.

this sounds difficult, if the server resides in a remote hosting company... as Jens anlready pointed out, the backup still resides on the remote machine and you have the hoster to provide a way (say a remote folder you can access over FTP) to bring it home...

regards

HELP - need to kill big transaction that's taking too long to rollback

Hi all,
I have a big transaction running on a table that I had to kill and
rollback. Unfortunately, the transaction has been rolling back for 1.5
hours and is supposedly only 6% done rolling back. I need to stop this
transaction, and I'm looking for the fastest way to do it with doing
the least amount of damage.
Is there any nuke button that I can press to kill this process with
extreme prejudice? - at this point I don't care about the integrity of
the table I was running the transaction on - I just want it to die.
Is there any way to force the table to drop, thus killing the process?
Is there any way to make a new log file for this database, and kill the
log file that has the rolling back?
If I stop SQL Server, will it try to wait until the transaction is
done/rolledback before it will actually stop?
Please HELP! Thanks in advance
-Rob
Stop the server service?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"robh1999atgmail" <RobH1999@.gmail.com> wrote in message
news:1159460802.483348.29370@.d34g2000cwd.googlegro ups.com...
> Hi all,
> I have a big transaction running on a table that I had to kill and
> rollback. Unfortunately, the transaction has been rolling back for 1.5
> hours and is supposedly only 6% done rolling back. I need to stop this
> transaction, and I'm looking for the fastest way to do it with doing
> the least amount of damage.
> Is there any nuke button that I can press to kill this process with
> extreme prejudice? - at this point I don't care about the integrity of
> the table I was running the transaction on - I just want it to die.
> Is there any way to force the table to drop, thus killing the process?
>
> Is there any way to make a new log file for this database, and kill the
> log file that has the rolling back?
> If I stop SQL Server, will it try to wait until the transaction is
> done/rolledback before it will actually stop?
> Please HELP! Thanks in advance
> -Rob
>

HELP - need to kill big transaction that's taking too long to rollback

Hi all,
I have a big transaction running on a table that I had to kill and
rollback. Unfortunately, the transaction has been rolling back for 1.5
hours and is supposedly only 6% done rolling back. I need to stop this
transaction, and I'm looking for the fastest way to do it with doing
the least amount of damage.
Is there any nuke button that I can press to kill this process with
extreme prejudice? - at this point I don't care about the integrity of
the table I was running the transaction on - I just want it to die.
Is there any way to force the table to drop, thus killing the process?
Is there any way to make a new log file for this database, and kill the
log file that has the rolling back?
If I stop SQL Server, will it try to wait until the transaction is
done/rolledback before it will actually stop?
Please HELP! Thanks in advance
-RobStop the server service?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"robh1999atgmail" <RobH1999@.gmail.com> wrote in message
news:1159460802.483348.29370@.d34g2000cwd.googlegroups.com...
> Hi all,
> I have a big transaction running on a table that I had to kill and
> rollback. Unfortunately, the transaction has been rolling back for 1.5
> hours and is supposedly only 6% done rolling back. I need to stop this
> transaction, and I'm looking for the fastest way to do it with doing
> the least amount of damage.
> Is there any nuke button that I can press to kill this process with
> extreme prejudice? - at this point I don't care about the integrity of
> the table I was running the transaction on - I just want it to die.
> Is there any way to force the table to drop, thus killing the process?
>
> Is there any way to make a new log file for this database, and kill the
> log file that has the rolling back?
> If I stop SQL Server, will it try to wait until the transaction is
> done/rolledback before it will actually stop?
> Please HELP! Thanks in advance
> -Rob
>

HELP - need to kill big transaction that's taking too long to rollback

Hi all,
I have a big transaction running on a table that I had to kill and
rollback. Unfortunately, the transaction has been rolling back for 1.5
hours and is supposedly only 6% done rolling back. I need to stop this
transaction, and I'm looking for the fastest way to do it with doing
the least amount of damage.
Is there any nuke button that I can press to kill this process with
extreme prejudice? - at this point I don't care about the integrity of
the table I was running the transaction on - I just want it to die.
Is there any way to force the table to drop, thus killing the process?
Is there any way to make a new log file for this database, and kill the
log file that has the rolling back?
If I stop SQL Server, will it try to wait until the transaction is
done/rolledback before it will actually stop?
Please HELP! Thanks in advance
-RobStop the server service?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"robh1999atgmail" <RobH1999@.gmail.com> wrote in message
news:1159460802.483348.29370@.d34g2000cwd.googlegroups.com...
> Hi all,
> I have a big transaction running on a table that I had to kill and
> rollback. Unfortunately, the transaction has been rolling back for 1.5
> hours and is supposedly only 6% done rolling back. I need to stop this
> transaction, and I'm looking for the fastest way to do it with doing
> the least amount of damage.
> Is there any nuke button that I can press to kill this process with
> extreme prejudice? - at this point I don't care about the integrity of
> the table I was running the transaction on - I just want it to die.
> Is there any way to force the table to drop, thus killing the process?
>
> Is there any way to make a new log file for this database, and kill the
> log file that has the rolling back?
> If I stop SQL Server, will it try to wait until the transaction is
> done/rolledback before it will actually stop?
> Please HELP! Thanks in advance
> -Rob
>

HELP

HOLY @.#$% HOLY #$*&
MY SERVER IS COMPLETELY CORRUPT AND MY BACK UP SERVER WON'T
BOOT!!!!
IS THIS A HACKER PROBLEM!!!!'"Colin Bissbort" <anonymous@.discussions.microsoft.com> wrote in message
news:001601c3d3b8$48550340$a501280a@.phx.gbl...

quote:

---

> HOLY @.#$% HOLY #$*&
> MY SERVER IS COMPLETELY CORRUPT AND MY BACK UP SERVER WON'T
> BOOT!!!!
> IS THIS A HACKER PROBLEM!!!!'

---

That is a possibility -- however, you also need to rule out a hardware issue
as well...
Steve