Showing posts with label moved. Show all posts
Showing posts with label moved. Show all posts

Friday, March 23, 2012

Moving 2005 Resource Database

We have a sql 2005 installation that has service pack 2 applied. All
the system databases apart from the resource database have been moved
from the default data directory to our own data directory on a
seperate drive and this went ok. We've done this basically to make the
back up process more efficient in our environment. The issue is that
we cant find a way to move the resource database to the new location
and this I beleive needs to be kept with the master database. We've
followed the BOL instructions for moving system databases but the
Alter script for the resource database fails as the resource database
doesnt exist in sysdatabases. I've tried simply moving the resource
files to the new location but then sql wont start as it cant find the
files.
Anybody have any ideas how to resolve this issue?
Thanks
MichaelThe instructions in Books Online for moving the master and resource database
files should work. However, we made some corrections to the procedure in
April 2006. If you don't have the latest version of Books Online, you might
be running into a problem.
I suggest that you download the latest version fo BOL (see the link in my
signature) and then starting with step 7 (Start the instance of SQL Server
in master-only recovery mode...), see if you can get the resource database
moved. If you still run into trouble, please report the exact error
message you're getting.
Regards,
Gail
--
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://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
"Michael" <michael@.hampel.fsnet.co.uk> wrote in message
news:1183985960.779841.257510@.k79g2000hse.googlegroups.com...
> We have a sql 2005 installation that has service pack 2 applied. All
> the system databases apart from the resource database have been moved
> from the default data directory to our own data directory on a
> seperate drive and this went ok. We've done this basically to make the
> back up process more efficient in our environment. The issue is that
> we cant find a way to move the resource database to the new location
> and this I beleive needs to be kept with the master database. We've
> followed the BOL instructions for moving system databases but the
> Alter script for the resource database fails as the resource database
> doesnt exist in sysdatabases. I've tried simply moving the resource
> files to the new location but then sql wont start as it cant find the
> files.
> Anybody have any ideas how to resolve this issue?
> Thanks
> Michael
>sql

moved stock minus in item table to stock in itemmoment table

helo all...,


i want to make procedure like:
example

i have table:
item (itemid,itemname,stock)
orderdetail(no_order,itemid,quantity)
itemmoment(itemid,itemname,stock)
item table
itemid itemname stock
c1 coconut 2
p1 peanut 2

orderdetail table
no_order itemid quantity
1 c1 5

itemmoment table
itemid itemname stock
c1 coconut 0
p1 peanut 0

when customer paid, his quantity in orderdetail decrease stock in item table..
so stock in item table became:
itemid itemname stock
c1 coconut -3
p1 peanut 2

it's not good, because stock may not minus...
so i want to move -3 to itemmoment table..
so stock in item table became:
itemid itemname stock
c1 coconut 0
p1 peanut 2

and in itemmoment table became:
itemid itemname stock
c1 coconut 3
p1 peanut 0

my store procedure like:
ALTER PROCEDURE [dbo].[orders]
(
@.no_order as integer,
@.itemid AS varchar(50),
@.quantity AS INT
)
AS
BEGIN
BEGIN TRANSACTION

DECLARE @.currentStock AS INT


SET @.currentStock = (SELECT [Stok] FROM [item] WHERE [itemid] = @.itemid)

UPDATE [item]
SET
[Stock] = @.currentStock - @.quantity
WHERE
[itemid] = @.itemid

COMMIT TRANSACTION
END

it's only decrease stock with quantity. i want move stock minus from item to itemmoment..
can anyone add code to my store procedure?

plss.. helpp.
thxx...

Here's how you would tackle the issue.

Declare @.AvailableQtySelect @.AvailableQty =Count(*)FROM ItemWhere ItemId = @.ItemIdIF @.AvailableQty >= @.QuantityBegin-- We have enough quantityUpdate ItemSet Stock = Stock - @.QuantityWhere ItemId = @.ItemIdEndElseBegin-- We have less quantityUpdate ItemSet Stock = 0Where ItemId = @.ItemIdInsert into ItemMoment (itemid,itemname, stock )Select @.ItemId, ItemName, (@.Quantity - @.AvailableQty )From ItemWhere Itemid = @.ItemIdEnd
|||

thx ndinakar...

it's one problem in ur store procedure, but i have fix it.

Select @.AvailableQty =Count(*)FROM ItemWhere ItemId = @.ItemId
change to
set @.AvailableQty = (select stock FROM item Where itemid = @.itemid) 

it have working...

ok, thx...

Moved SQL to the new box

Hi everybody,

I re-built SQl server 2000 on the new box. Attached and detached all DBs (master, msdb, users DBs) and moved them to the new paths (E:\mssql). Everything is fine.

The questions are:
1. The 'filename' in the master.sysdatabases for 'master' DB is still pointed to the old location (F:\) even physicaly files are on E:\ drive;

2. The 'phyname' in the master.sysdevices for all devices (DBs), including master, msdb, model are still shows the old location (F:\);
At list I will get a wrong reports of the files location.

it could be other places in the system tables that keep old information.
How and where I can correct the information?

3. All jobs, bakups, etc. that creates output files still pointed to the old locations (let say to the F:\sql2000\). F:\ drive is not exists anymore.
I will recreate all jobs and main plans to specify correct path.
But how can I change the DEFAULT locations for all backups, logs, etc. ?

Thank you,
LYOne way you could do it (sorry but its a bit long winded), is to create your dbs on the new server and restore the dbs you wish to move, using the "with move" clause on the resore database command.

By virtue of the fact you have created the dbs on the new server your paths should be OK, and not inherited by the dbs you sp_attach_db'ed

Hope this helps|||In the rebuild situation, I generally will not restore or reattach system databases, only the user databases. Because my past experience of having numerous troubles with the master after restoring to a new machine. Scheduled tasks and DTS can be saved and transfer to the new machine.

Good luck!|||Originally posted by dbabren
One way you could do it (sorry but its a bit long winded), is to create your dbs on the new server and restore the dbs you wish to move, using the "with move" clause on the resore database command.

By virtue of the fact you have created the dbs on the new server your paths should be OK, and not inherited by the dbs you sp_attach_db'ed

Hope this helps

=====

All user DB's are fine.
The only incorrect information for master.sysdatabases.filename (for master database) and master.sysdevices (for all devices).

Thank you.
LYsql

Moved SQL Server to different server

Our techs moved sql server over to a different server thats solely for sql and now the backups wont work right, they check for the consistency but wont back up the data. Can anyone give some suggestions pleaseWhat is the path they are trying to back up to?

What is the error you are getting?|||He says he is trying to backup from gcfs01 drive to gcsql drive and the error message he is getting is Device cannot be found|||Sounds to me like he is trying to back up to a network drive that is not connected to the new server.

Backing up to a network drive is a bad idea, in my opinion. You should backup to a local drive, and then copy the resulting files to a network drive or to tape for archiving.|||he is putting SQL on to a server all its own, so he is moving it from gcfs01 server to gcsql server. Its been functioning and backing up to the gcfs01 server with no problems|||So what do you think is the issue there

How are you doing blindman? btw|||Doing fine, thank you.

He needs to open up windows exporer and make sure he can access both those drives under SQL Agent's account.

Again, you should backup your databases to a local drive, referenced by the drive letter. I do not understand what you mean by "he is trying to backup from gcfs01 drive to gcsql drive".|||If you are trying to move the backup off the server, then backup locally, zip the file and then move the file. You will only need enough free space as large as the biggest backup+the zip file. Backing up to a network drive is much much slower and not as stable as backing up locally.

I backup all of my databases, zip them, and have them copied to my machine nightly. That way when I come in in the morning I have everything I need to recreate all my databases on my machine.

Just my opinion.|||Just my opinion...and the opinion of every other experienced dba. I don't know of anybody who would recommend backing up directly to a network drive.|||...and the opinion of every other experienced dba. I don't know of anybody who would recommend backing up directly to a network drive.Its Ok with me for a few manual "one off" situations, particularly in actual process of migrating to a new machine. I wouldn't recommend it for an ongoing practice, especially not an automated one.

-PatP|||You guys are such a great I really appreciate it :)

No I was just reiterating what I said earlier, I didnt know if explained correctly or anything. Let me tell him what you guys are saying

YOUR THE BEST|||so blind what your saying is instead of backing it up to the server, back it up to a local drive instead??

says hes getting error messages from the backup tapes..hmm|||I have a scheduled job the backs up the databases to disk in separate subdirectories, maintaining five days of historical data on the local drive. A second step then uses robocopy to archive the new files off to a network drive, where our network administrator uses veritas to back them up to tape.

You should not backup to a network drive, because you do not want database recoverability to fail due to network failure. Plus, as was mentioned, it is slow.|||Our Tech is actually going to try it out, hes going to take your advice...HOORAY!!!!!!!!!!!

Moved SQL Server 2000 to 2005 and login is not attache

I recently moved a SQL Server 2000 server to 2005 and I cannot drop
the user. One of the issues is that the user does not have a login. I
tried to do an Alter USer but it's not sticking.
How can I add a login to an already created user?Check out sp_change_users_login in the BOL.
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
<axwack@.gmail.com> wrote in message
news:1177599478.863706.29390@.s33g2000prh.googlegroups.com...
I recently moved a SQL Server 2000 server to 2005 and I cannot drop
the user. One of the issues is that the user does not have a login. I
tried to do an Alter USer but it's not sticking.
How can I add a login to an already created user?|||ok do this.
use mydatabase
EXEC sp_change_users_login 'Report'
This outputs the users that are orpohaned.
Now run this to fix the user
Sp_change_users_login AUTO_FIX, myusername
This will get you going again.
John Vandervliet...
"axwack@.gmail.com" wrote:

> I recently moved a SQL Server 2000 server to 2005 and I cannot drop
> the user. One of the issues is that the user does not have a login. I
> tried to do an Alter USer but it's not sticking.
> How can I add a login to an already created user?
>

Moved SQL Server 2000 to 2005 and login is not attache

I recently moved a SQL Server 2000 server to 2005 and I cannot drop
the user. One of the issues is that the user does not have a login. I
tried to do an Alter USer but it's not sticking.
How can I add a login to an already created user?Check out sp_change_users_login in the BOL.
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
<axwack@.gmail.com> wrote in message
news:1177599478.863706.29390@.s33g2000prh.googlegroups.com...
I recently moved a SQL Server 2000 server to 2005 and I cannot drop
the user. One of the issues is that the user does not have a login. I
tried to do an Alter USer but it's not sticking.
How can I add a login to an already created user?|||ok do this.
use mydatabase
EXEC sp_change_users_login 'Report'
This outputs the users that are orpohaned.
Now run this to fix the user
Sp_change_users_login AUTO_FIX, myusername
This will get you going again.
John Vandervliet...
"axwack@.gmail.com" wrote:
> I recently moved a SQL Server 2000 server to 2005 and I cannot drop
> the user. One of the issues is that the user does not have a login. I
> tried to do an Alter USer but it's not sticking.
> How can I add a login to an already created user?
>

Moved SQL Server 2000 to 2005 and login is not attache

I recently moved a SQL Server 2000 server to 2005 and I cannot drop
the user. One of the issues is that the user does not have a login. I
tried to do an Alter USer but it's not sticking.
How can I add a login to an already created user?
Check out sp_change_users_login in the BOL.
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
https://mvp.support.microsoft.com/profile/Tom.Moreau
<axwack@.gmail.com> wrote in message
news:1177599478.863706.29390@.s33g2000prh.googlegro ups.com...
I recently moved a SQL Server 2000 server to 2005 and I cannot drop
the user. One of the issues is that the user does not have a login. I
tried to do an Alter USer but it's not sticking.
How can I add a login to an already created user?
|||ok do this.
use mydatabase
EXEC sp_change_users_login 'Report'
This outputs the users that are orpohaned.
Now run this to fix the user
Sp_change_users_login AUTO_FIX, myusername
This will get you going again.
John Vandervliet...
"axwack@.gmail.com" wrote:

> I recently moved a SQL Server 2000 server to 2005 and I cannot drop
> the user. One of the issues is that the user does not have a login. I
> tried to do an Alter USer but it's not sticking.
> How can I add a login to an already created user?
>

Moved SQL DB to SQL2005 and it is slow

Hello,
I moved a sql 2000 DB to SQL 2005 and it seems to be very slow.
The same DB on a slower machine running 2000 runs mutch faster.
For example one SP on 2000 takes 5 seconds but on SQL 2005 it takes 102
seconds, 20 times slower.
I reindexed and that did not help.
Any Ideas?
Why the same DB with same indexes behaving that way, what Am I missing'
This is the release version of sql2005, Stardard edition, RTM...
Thanks
SAAre you accessing the database from a .Net 1.1 application using the standar
d
SqlConnection / related classes? I found that my .NET 1.1 apps would not
connect to a SQL Server 2005 instance using a shared memory connection.
Recompiling the same code with the .NET 2.0 framework resolved the issue -
the application again connected using shared memory and was sigificantly
faster. I don't know how to go about determining what mode (tcp / names
pipes / shared memory) a given connection is using, but I'm sure a quick
search will answer that.
Ross
"MSDN" wrote:

> Hello,
> I moved a sql 2000 DB to SQL 2005 and it seems to be very slow.
> The same DB on a slower machine running 2000 runs mutch faster.
> For example one SP on 2000 takes 5 seconds but on SQL 2005 it takes 102
> seconds, 20 times slower.
> I reindexed and that did not help.
> Any Ideas?
> Why the same DB with same indexes behaving that way, what Am I missing'
'
> This is the release version of sql2005, Stardard edition, RTM...
>
> Thanks
> SA
>
>|||Have you run UPDATE TATISTICS with FULLSCAN option?
"MSDN" <sql_agentman@.hotmail.com> wrote in message
news:OD02m01NGHA.2668@.tk2msftngp13.phx.gbl...
> Hello,
> I moved a sql 2000 DB to SQL 2005 and it seems to be very slow.
> The same DB on a slower machine running 2000 runs mutch faster.
> For example one SP on 2000 takes 5 seconds but on SQL 2005 it takes 102
> seconds, 20 times slower.
> I reindexed and that did not help.
> Any Ideas?
> Why the same DB with same indexes behaving that way, what Am I
> missing'
> This is the release version of sql2005, Stardard edition, RTM...
>
> Thanks
> SA
>|||Sorry
UPDATE STATISTICS
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:OMQ9gf3NGHA.3864@.TK2MSFTNGP10.phx.gbl...
> Have you run UPDATE TATISTICS with FULLSCAN option?
>
>
> "MSDN" <sql_agentman@.hotmail.com> wrote in message
> news:OD02m01NGHA.2668@.tk2msftngp13.phx.gbl...
>|||MSDN (sql_agentman@.hotmail.com) writes:
> I moved a sql 2000 DB to SQL 2005 and it seems to be very slow.
> The same DB on a slower machine running 2000 runs mutch faster.
> For example one SP on 2000 takes 5 seconds but on SQL 2005 it takes 102
> seconds, 20 times slower.
> I reindexed and that did not help.
> Any Ideas?
> Why the same DB with same indexes behaving that way, what Am I
> missing'
As Uri pointed you must run UPDATE STATISTICS WITH FULLSCAN on all your
tables. The statistics from SQL 2000 are invalidated when you upgrade.
There may be more to it than that, but start there.
If you need further assistence, please be more specific of what is slow.
Is it certain queries, or is it slower overall? If you run queries from
Query Analyzer, is there still any differences (to rule out connection
issues as suggested in Ross's post). If you run from the local machine
(to exclude network issues)?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Perhaps it's not the database, but configuration of the SQL Server
installation. Also, if this database is running on a new server box, it may
be related hardware or OS configuration.
The following was copied from the MSDN article titled: Checklist: SQL Server
Performance
Use default server configuration settings for most applications.
Locate logs and the tempdb database on separate devices from the data.
Provide separate devices for heavily accessed tables and indexes.
Use the correct RAID configuration.
Use multiple disk controllers.
Pre-grow databases and logs to avoid automatic growth and fragmentation
performance impact.
Maximize available memory.
Manage index fragmentation.
Keep database administrator tasks in mind.
http://msdn.microsoft.com/SQL/2000/...enetcheck08.asp
"MSDN" <sql_agentman@.hotmail.com> wrote in message
news:OD02m01NGHA.2668@.tk2msftngp13.phx.gbl...
> Hello,
> I moved a sql 2000 DB to SQL 2005 and it seems to be very slow.
> The same DB on a slower machine running 2000 runs mutch faster.
> For example one SP on 2000 takes 5 seconds but on SQL 2005 it takes 102
> seconds, 20 times slower.
> I reindexed and that did not help.
> Any Ideas?
> Why the same DB with same indexes behaving that way, what Am I
> missing'
> This is the release version of sql2005, Stardard edition, RTM...
>
> Thanks
> SA
>sql

Moved Server and Now Subscriptions Gone

edited

edited

Moved master db and now cannot start SQL

After changing the startup parameters and moving the database we are unable
to start SQL. The error message we are getting in the application log is
that the initconfig: (error 5) access denied to g:\sqldata.
HI,
How u moved the database and what parameter u have changed.
from
killer
Ray Skweres wrote:
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.
|||Hi
This article descibes how to move your master database
http://support.microsoft.com/kb/224071/EN-US/
You may want to try starting SQL Server from the command prompt
http://msdn.microsoft.com/library/de...servr_4apa.asp
with the correct parameters (possibly with -f also!) and also making sure
that the permissions for the directories being used are correct.
You can not use a mapped network drive for your database files.
John
"Ray Skweres" wrote:

> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.
|||Error 5 is access denied. Make sure that the SQL Server service account has permissions to the file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:2053CEEC-32D3-4840-9898-D59433C29617@.microsoft.com...
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.
|||Moved it based on Microsoft articel changed startup parameters and only moved
the master.mdf so I only changed that parameter.
"doller" wrote:

> HI,
> How u moved the database and what parameter u have changed.
> from
> killer
>
> Ray Skweres wrote:
>
|||Used this article to move the database also tried to start it from a command
prompt and would not start. Also tried to change the startup parameters back
though command prompt and did not work. I am not using a mapped network
drive. Permissions are fine on the file. Even went into registry and tried
to change and then start sql still did not start and then when I went back
into the registry and it was back to the old setting.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This article descibes how to move your master database
> http://support.microsoft.com/kb/224071/EN-US/
> You may want to try starting SQL Server from the command prompt
> http://msdn.microsoft.com/library/de...servr_4apa.asp
> with the correct parameters (possibly with -f also!) and also making sure
> that the permissions for the directories being used are correct.
> You can not use a mapped network drive for your database files.
> John
> "Ray Skweres" wrote:
|||Hi
Are you using the -d and -l parameters when starting on the command prompt?
Is there any privacy or anti-virus software running?
You may want to try reverting back to the previous location and see if it
starts.
If have backed up all your databases then you may want to try un-installing
and re-installing. You should be able to attach the databases from the
mdf/ldf files, but you will need to re-instate logins and jobs.
John
"Ray Skweres" wrote:
[vbcol=seagreen]
> Used this article to move the database also tried to start it from a command
> prompt and would not start. Also tried to change the startup parameters back
> though command prompt and did not work. I am not using a mapped network
> drive. Permissions are fine on the file. Even went into registry and tried
> to change and then start sql still did not start and then when I went back
> into the registry and it was back to the old setting.
> "John Bell" wrote:
|||Whether your the service account you are starting has access to the
g:\sqldata.
Thanks
Ajay Rengunthwar
MCDBA, MCAD
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:19FD3DAA-35C5-482E-B0CD-FA8068B7FA71@.microsoft.com...
> Moved it based on Microsoft articel changed startup parameters and only
moved[vbcol=seagreen]
> the master.mdf so I only changed that parameter.
> "doller" wrote:
unable[vbcol=seagreen]
log is[vbcol=seagreen]
|||Hi
Another thought, have you checked for disc corruption?
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:BFC7ACBD-19F4-4714-919B-C7774A17FFC7@.microsoft.com...[vbcol=seagreen]
> Hi
> Are you using the -d and -l parameters when starting on the command
> prompt?
> Is there any privacy or anti-virus software running?
> You may want to try reverting back to the previous location and see if it
> starts.
> If have backed up all your databases then you may want to try
> un-installing
> and re-installing. You should be able to attach the databases from the
> mdf/ldf files, but you will need to re-instate logins and jobs.
>
> John
> "Ray Skweres" wrote:

Moved master db and now cannot start SQL

After changing the startup parameters and moving the database we are unable
to start SQL. The error message we are getting in the application log is
that the initconfig: (error 5) access denied to g:\sqldata.HI,
How u moved the database and what parameter u have changed.
from
killer
Ray Skweres wrote:
> After changing the startup parameters and moving the database we are unabl
e
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Hi
This article descibes how to move your master database
http://support.microsoft.com/kb/224071/EN-US/
You may want to try starting SQL Server from the command prompt
http://msdn.microsoft.com/library/d...>
rvr_4apa.asp
with the correct parameters (possibly with -f also!) and also making sure
that the permissions for the directories being used are correct.
You can not use a mapped network drive for your database files.
John
"Ray Skweres" wrote:

> After changing the startup parameters and moving the database we are unabl
e
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Error 5 is access denied. Make sure that the SQL Server service account has
permissions to the file.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:2053CEEC-32D3-4840-9898-D59433C29617@.microsoft.com...
> After changing the startup parameters and moving the database we are unabl
e
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Moved it based on Microsoft articel changed startup parameters and only move
d
the master.mdf so I only changed that parameter.
"doller" wrote:

> HI,
> How u moved the database and what parameter u have changed.
> from
> killer
>
> Ray Skweres wrote:
>|||Used this article to move the database also tried to start it from a command
prompt and would not start. Also tried to change the startup parameters bac
k
though command prompt and did not work. I am not using a mapped network
drive. Permissions are fine on the file. Even went into registry and tried
to change and then start sql still did not start and then when I went back
into the registry and it was back to the old setting.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This article descibes how to move your master database
> http://support.microsoft.com/kb/224071/EN-US/
> You may want to try starting SQL Server from the command prompt
> http://msdn.microsoft.com/library/d...
servr_4apa.asp
> with the correct parameters (possibly with -f also!) and also making sure
> that the permissions for the directories being used are correct.
> You can not use a mapped network drive for your database files.
> John
> "Ray Skweres" wrote:
>|||Hi
Are you using the -d and -l parameters when starting on the command prompt?
Is there any privacy or anti-virus software running?
You may want to try reverting back to the previous location and see if it
starts.
If have backed up all your databases then you may want to try un-installing
and re-installing. You should be able to attach the databases from the
mdf/ldf files, but you will need to re-instate logins and jobs.
John
"Ray Skweres" wrote:
[vbcol=seagreen]
> Used this article to move the database also tried to start it from a comma
nd
> prompt and would not start. Also tried to change the startup parameters b
ack
> though command prompt and did not work. I am not using a mapped network
> drive. Permissions are fine on the file. Even went into registry and trie
d
> to change and then start sql still did not start and then when I went back
> into the registry and it was back to the old setting.
> "John Bell" wrote:
>|||Whether your the service account you are starting has access to the
g:\sqldata.
Thanks
Ajay Rengunthwar
MCDBA, MCAD
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:19FD3DAA-35C5-482E-B0CD-FA8068B7FA71@.microsoft.com...
> Moved it based on Microsoft articel changed startup parameters and only
moved[vbcol=seagreen]
> the master.mdf so I only changed that parameter.
> "doller" wrote:
>
unable[vbcol=seagreen]
log is[vbcol=seagreen]|||Hi
Another thought, have you checked for disc corruption?
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:BFC7ACBD-19F4-4714-919B-C7774A17FFC7@.microsoft.com...[vbcol=seagreen]
> Hi
> Are you using the -d and -l parameters when starting on the command
> prompt?
> Is there any privacy or anti-virus software running?
> You may want to try reverting back to the previous location and see if it
> starts.
> If have backed up all your databases then you may want to try
> un-installing
> and re-installing. You should be able to attach the databases from the
> mdf/ldf files, but you will need to re-instate logins and jobs.
>
> John
> "Ray Skweres" wrote:
>

Moved master db and now cannot start SQL

After changing the startup parameters and moving the database we are unable
to start SQL. The error message we are getting in the application log is
that the initconfig: (error 5) access denied to g:\sqldata.HI,
How u moved the database and what parameter u have changed.
from
killer
Ray Skweres wrote:
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Hi
This article descibes how to move your master database
http://support.microsoft.com/kb/224071/EN-US/
You may want to try starting SQL Server from the command prompt
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
with the correct parameters (possibly with -f also!) and also making sure
that the permissions for the directories being used are correct.
You can not use a mapped network drive for your database files.
John
"Ray Skweres" wrote:
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Error 5 is access denied. Make sure that the SQL Server service account has permissions to the file.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:2053CEEC-32D3-4840-9898-D59433C29617@.microsoft.com...
> After changing the startup parameters and moving the database we are unable
> to start SQL. The error message we are getting in the application log is
> that the initconfig: (error 5) access denied to g:\sqldata.|||Moved it based on Microsoft articel changed startup parameters and only moved
the master.mdf so I only changed that parameter.
"doller" wrote:
> HI,
> How u moved the database and what parameter u have changed.
> from
> killer
>
> Ray Skweres wrote:
> > After changing the startup parameters and moving the database we are unable
> > to start SQL. The error message we are getting in the application log is
> > that the initconfig: (error 5) access denied to g:\sqldata.
>|||Used this article to move the database also tried to start it from a command
prompt and would not start. Also tried to change the startup parameters back
though command prompt and did not work. I am not using a mapped network
drive. Permissions are fine on the file. Even went into registry and tried
to change and then start sql still did not start and then when I went back
into the registry and it was back to the old setting.
"John Bell" wrote:
> Hi
> This article descibes how to move your master database
> http://support.microsoft.com/kb/224071/EN-US/
> You may want to try starting SQL Server from the command prompt
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
> with the correct parameters (possibly with -f also!) and also making sure
> that the permissions for the directories being used are correct.
> You can not use a mapped network drive for your database files.
> John
> "Ray Skweres" wrote:
> > After changing the startup parameters and moving the database we are unable
> > to start SQL. The error message we are getting in the application log is
> > that the initconfig: (error 5) access denied to g:\sqldata.|||Hi
Are you using the -d and -l parameters when starting on the command prompt?
Is there any privacy or anti-virus software running?
You may want to try reverting back to the previous location and see if it
starts.
If have backed up all your databases then you may want to try un-installing
and re-installing. You should be able to attach the databases from the
mdf/ldf files, but you will need to re-instate logins and jobs.
John
"Ray Skweres" wrote:
> Used this article to move the database also tried to start it from a command
> prompt and would not start. Also tried to change the startup parameters back
> though command prompt and did not work. I am not using a mapped network
> drive. Permissions are fine on the file. Even went into registry and tried
> to change and then start sql still did not start and then when I went back
> into the registry and it was back to the old setting.
> "John Bell" wrote:
> > Hi
> >
> > This article descibes how to move your master database
> > http://support.microsoft.com/kb/224071/EN-US/
> >
> > You may want to try starting SQL Server from the command prompt
> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
> > with the correct parameters (possibly with -f also!) and also making sure
> > that the permissions for the directories being used are correct.
> >
> > You can not use a mapped network drive for your database files.
> >
> > John
> >
> > "Ray Skweres" wrote:
> >
> > > After changing the startup parameters and moving the database we are unable
> > > to start SQL. The error message we are getting in the application log is
> > > that the initconfig: (error 5) access denied to g:\sqldata.|||Whether your the service account you are starting has access to the
g:\sqldata.
Thanks
Ajay Rengunthwar
MCDBA, MCAD
"Ray Skweres" <RaySkweres@.discussions.microsoft.com> wrote in message
news:19FD3DAA-35C5-482E-B0CD-FA8068B7FA71@.microsoft.com...
> Moved it based on Microsoft articel changed startup parameters and only
moved
> the master.mdf so I only changed that parameter.
> "doller" wrote:
> > HI,
> > How u moved the database and what parameter u have changed.
> >
> > from
> > killer
> >
> >
> > Ray Skweres wrote:
> > > After changing the startup parameters and moving the database we are
unable
> > > to start SQL. The error message we are getting in the application
log is
> > > that the initconfig: (error 5) access denied to g:\sqldata.
> >
> >|||Hi
Another thought, have you checked for disc corruption?
John
"John Bell" <jbellnewsposts@.hotmail.com> wrote in message
news:BFC7ACBD-19F4-4714-919B-C7774A17FFC7@.microsoft.com...
> Hi
> Are you using the -d and -l parameters when starting on the command
> prompt?
> Is there any privacy or anti-virus software running?
> You may want to try reverting back to the previous location and see if it
> starts.
> If have backed up all your databases then you may want to try
> un-installing
> and re-installing. You should be able to attach the databases from the
> mdf/ldf files, but you will need to re-instate logins and jobs.
>
> John
> "Ray Skweres" wrote:
>> Used this article to move the database also tried to start it from a
>> command
>> prompt and would not start. Also tried to change the startup parameters
>> back
>> though command prompt and did not work. I am not using a mapped network
>> drive. Permissions are fine on the file. Even went into registry and
>> tried
>> to change and then start sql still did not start and then when I went
>> back
>> into the registry and it was back to the old setting.
>> "John Bell" wrote:
>> > Hi
>> >
>> > This article descibes how to move your master database
>> > http://support.microsoft.com/kb/224071/EN-US/
>> >
>> > You may want to try starting SQL Server from the command prompt
>> > http://msdn.microsoft.com/library/default.asp?url=/library/en-us/coprompt/cp_sqlservr_4apa.asp
>> > with the correct parameters (possibly with -f also!) and also making
>> > sure
>> > that the permissions for the directories being used are correct.
>> >
>> > You can not use a mapped network drive for your database files.
>> >
>> > John
>> >
>> > "Ray Skweres" wrote:
>> >
>> > > After changing the startup parameters and moving the database we are
>> > > unable
>> > > to start SQL. The error message we are getting in the application
>> > > log is
>> > > that the initconfig: (error 5) access denied to g:\sqldata.

moved from ms sql 2000 to ms sql2005

database has been recently upgraded from ms sql 2000 to ms sql 2005.
are there anything I need to be aware after upgrading to ms sql 2005?

for my experience, i got an error if i use column alias in ORDER BY
clause which was fine on ms sql 200.

thanksHandersonVA (handersonva@.hotmail.com) writes:

Quote:

Originally Posted by

database has been recently upgraded from ms sql 2000 to ms sql 2005.
are there anything I need to be aware after upgrading to ms sql 2005?


Run sp_updatestats on all databases, since statistics from SQL 2000 are
invalidated with the upgrade.

Quote:

Originally Posted by

for my experience, i got an error if i use column alias in ORDER BY
clause which was fine on ms sql 200.


It's fine in SQL 2005 too. However, there were bugs in SQL 2000 which lead
to incorrect code being accepted. For instance in SQL 2000 you can
say:

SELECT name FROM sysobjects ORDER BY myownalias.name

This is correctly rejected in SQL 2005. There are a couple of variations
on this theme.

Another issue that has bitten more that one is that they had views
like:

CREATE VIEW myview AS
SELECT TOP 100 PERCENT ...
ORDER BY somecol

then they expect "SELECT ... FORM myview" to always return data ordered
by somecol. SQL 2000 usually honors that, which is mere chance. On
SQL 2005 you are less lucky. The moral is that you should always
specify an ORDER BY clause on SELECT statements that produces data.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspxsql

Moved database, need to set the login name for DBO.

Hello,
I have moved a database to a new server (DR scenario). I have sucessfully
recreated one of the SQL user accounts needed, but the other one (lets call
it ACCOUNT2) is more of a problem.
When I look at the users on the database in question, dbo should have a
login of ACCOUNT2. I can't figure out how to recreate this. ACCOUNT2
currently exists on the new server.
I have tried looking at SP_CHANGE_USERS_LOGIN but don't think it will do the
job.
Any ideas?
Cheers
Remember that you are an Englishman, and have consequently won first
prize in the lottery of life" -Cecil Rhodes
"For a century and a half now, America and Japan have formed one of the
great and enduring alliances of modern times."
George W Bush -Tokyo, Japan, Feb. 18, 2002
Happy shall he be, that taketh and dasheth thy little ones against the
stones. Psalms 137:9.
Behold, I will corrupt your seed, and spread dung upon your faces.
Malachi 2:3.
"He who rises up to kill us, we will pre-empt it and kill him first,"
- Ariel Sharon 8th May 2002See this kb.
314546 HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/?id=314546
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Kevin McDonnell [MSFT] <kevmc@.online.microsoft.com> wrote:
> See this kb.
> 314546 HOW TO: Move Databases Between Computers That Are Running SQL
> Server http://support.microsoft.com/?id=314546
Thanks very much.
Remember that you are an Englishman, and have consequently won first
prize in the lottery of life" -Cecil Rhodes
"For a century and a half now, America and Japan have formed one of the
great and enduring alliances of modern times."
George W Bush -Tokyo, Japan, Feb. 18, 2002
Happy shall he be, that taketh and dasheth thy little ones against the
stones. Psalms 137:9.
Behold, I will corrupt your seed, and spread dung upon your faces.
Malachi 2:3.
"He who rises up to kill us, we will pre-empt it and kill him first,"
- Ariel Sharon 8th May 2002

Moved database to new server...before creating logins

I feel like an idiot for this.
We are moving our SQL Server database (2000 Standard) to a new server
(also 2000 standard--don't worry, we've got a separate license for it).
What I did was backup the database on the old server and restore it to
the new server for testing our software application.
Only problem is, I didn't create the users beforehand, so now I can't
log into the new server with the login. It says I can't access my
default database.
WIthout dropping the database, is there a way I can fix this? It would
be easy enough to drop and re-restore the database, but if there is a
shorter way that would also work just as well, please enlighten me.Sure there are several articles here that cover this and more. But at the
least you can just create a new Login and then use sp_change_users_login to
map the user to the login.
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://www.databasejournal.com/feat...cle.php/3379901 Moving
system DB's
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://support.microsoft.com/?id=221465 Using WITH MOVE in a
Restore
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
Andrew J. Kelly SQL MVP
"Brent White" <bwhite@.badgersportswear.com> wrote in message
news:1131724756.657385.127960@.f14g2000cwb.googlegroups.com...
>I feel like an idiot for this.
> We are moving our SQL Server database (2000 Standard) to a new server
> (also 2000 standard--don't worry, we've got a separate license for it).
> What I did was backup the database on the old server and restore it to
> the new server for testing our software application.
> Only problem is, I didn't create the users beforehand, so now I can't
> log into the new server with the login. It says I can't access my
> default database.
> WIthout dropping the database, is there a way I can fix this? It would
> be easy enough to drop and re-restore the database, but if there is a
> shorter way that would also work just as well, please enlighten me.
>|||Hi,
i found a good article by Mr. Vyas ,a very famous SQL Professional :
http://vyaskn.tripod.com/moving_sql_server.htm
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"Brent White" wrote:

> I feel like an idiot for this.
> We are moving our SQL Server database (2000 Standard) to a new server
> (also 2000 standard--don't worry, we've got a separate license for it).
> What I did was backup the database on the old server and restore it to
> the new server for testing our software application.
> Only problem is, I didn't create the users beforehand, so now I can't
> log into the new server with the login. It says I can't access my
> default database.
> WIthout dropping the database, is there a way I can fix this? It would
> be easy enough to drop and re-restore the database, but if there is a
> shorter way that would also work just as well, please enlighten me.
>

Moved asp.net app to network share, cant access SQL

I've recently moved an asp.net website from my PC to a network share because another tech it going to be working on it. I finally got the correct permissions on the network share and the correct .NET Framework settings on my PC to be able to run the app. Now I can't access the SQL server which is on a different server. Getting the following error:

Request for the permission of type 'System.Data.SqlClient.SqlClientPermission, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.

How to I setup access to my SQL server for the app from any given PC on my LAN?

Your current error is not SQL Server permissions but CAS(code access security) you have to fix that before, you can get the error related to SQL Server permissions if any. The two links below covers the issues related to your error. Hope this helps.

http://forums.asp.net/thread/1522588.aspx

http://blogs.msdn.com/shawnfa/archive/2003/06/20/57023.aspx

Monday, March 19, 2012

Move SQL Server Management Studio Startup folder

Hello,
I recently moved the two following folders (SQL Server Management Studio,
Visual Studio 2005) to another directory but got the following error:
...Import and Export Settings tools Options page. The IDE will use your
most recent setting for this session
When I opened Enterprise Manager, it recreated the folders. I went to
Tools/Options, but couldn't find the option to change the start up location.
Any assistance with this would be appreciated.
--
Thanks in advance,
sck10Hi sck,
Thanks for using MSDN Managed Newsgroup Support.
By default, the SQL Management Studio is located at %Program Files
%\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe. If you
moved the SQL Management Studio, please go to the folder and find the
SqlWb.exe application. What's the result? Do you get any error message?
Please provide the entire error so that we may do the further troubleshoot.
Basically, we do not recommand move the SQL Management Studio folder and
the Visual Studio 2005 folder directly. This may cause some application
could not found the referenced files. The best way to move these folder is
re-install the Visual Studio and the SQL Management Studio.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei Lu,
I am referencing the folders that SS2K5 makes in the "My Documents" and
where can I change the pointer to another directory.
C:\Documents and Settings\sck10\My Documents\SQL Server Management Studio
Backup
Code Snippets
Projects
Settings
Templates
Thanks,
sck10
"Wei Lu" <weilu@.online.microsoft.com> wrote in message
news:nSxQTvBaGHA.880@.TK2MSFTNGXA01.phx.gbl...
> Hi sck,
> Thanks for using MSDN Managed Newsgroup Support.
> By default, the SQL Management Studio is located at %Program Files
> %\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe. If you
> moved the SQL Management Studio, please go to the folder and find the
> SqlWb.exe application. What's the result? Do you get any error message?
> Please provide the entire error so that we may do the further
troubleshoot.
> Basically, we do not recommand move the SQL Management Studio folder and
> the Visual Studio 2005 folder directly. This may cause some application
> could not found the referenced files. The best way to move these folder is
> re-install the Visual Studio and the SQL Management Studio.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no
rights.
>|||Hi sck10,
Thanks for the update.
My understanding of your issue is: You want to specify the location when
you create a project/ solution in SQL Management Studio. If I misunderstood
your concern, please feel free to let me know.
You could change the location where your Project store in the location
textbox. Also you can Browse to the location you want to store the project.
By default, SQL Management Studio will create the project in the My
Documents\SQL Server Management Studio\Projects folder.
Hope this will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "sck10" <sck10@.online.nospam>
>References: <#fQKPj6ZGHA.4116@.TK2MSFTNGP05.phx.gbl>
<nSxQTvBaGHA.880@.TK2MSFTNGXA01.phx.gbl>
>Subject: Re: Move SQL Server Management Studio Startup folder
>Date: Wed, 26 Apr 2006 08:52:15 -0500
>Lines: 49
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
>Message-ID: <eGEohiTaGHA.1240@.TK2MSFTNGP03.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 11.202.185.135.in-addr.arpa 135.185.202.11
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:429301
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi Wei Lu,
>I am referencing the folders that SS2K5 makes in the "My Documents" and
>where can I change the pointer to another directory.
>C:\Documents and Settings\sck10\My Documents\SQL Server Management Studio
>Backup
>Code Snippets
>Projects
>Settings
>Templates
>Thanks,
>sck10
>"Wei Lu" <weilu@.online.microsoft.com> wrote in message
>news:nSxQTvBaGHA.880@.TK2MSFTNGXA01.phx.gbl...
>> Hi sck,
>> Thanks for using MSDN Managed Newsgroup Support.
>> By default, the SQL Management Studio is located at %Program Files
>> %\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\SqlWb.exe. If
you
>> moved the SQL Management Studio, please go to the folder and find the
>> SqlWb.exe application. What's the result? Do you get any error message?
>> Please provide the entire error so that we may do the further
>troubleshoot.
>> Basically, we do not recommand move the SQL Management Studio folder and
>> the Visual Studio 2005 folder directly. This may cause some application
>> could not found the referenced files. The best way to move these folder
is
>> re-install the Visual Studio and the SQL Management Studio.
>> Sincerely,
>> Wei Lu
>> Microsoft Online Community Support
>> ==================================================>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>> ==================================================>> This posting is provided "AS IS" with no warranties, and confers no
>rights.
>
>|||I have the same problem. Allow me to restate the issue from my point of
view, and maybe someone has an answer:
When I am in Management Studio and choose File... Open... File, the
standard Open File dialog box lists 3 icons in the left side: Desktop, My
Projects, and My Computer. The My Projects folder points to My Documents/SQL
Server Management Studio/My Projects.
I understand that this is the default location. I would like to CHANGE the
default location to a different folder.
There doesn't seem to be an option to set this default location in the
Management Studio Options. I tried to find the reference in the registry,
but cannot.
Alternatively, I would be happy to be able to ADD my preferred folder to
this dialog

Move SQL Server Management Studio Startup folder

Hello,
I recently moved the two following folders (SQL Server Management Studio,
Visual Studio 2005) to another directory but got the following error:
..Import and Export Settings tools Options page. The IDE will use your
most recent setting for this session
When I opened Enterprise Manager, it recreated the folders. I went to
Tools/Options, but couldn't find the option to change the start up location.
Any assistance with this would be appreciated.
--
Thanks in advance,
sck10Hi sck,
Thanks for using MSDN Managed Newsgroup Support.
By default, the SQL Management Studio is located at %Program Files
%\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE
\SqlWb.exe. If you
moved the SQL Management Studio, please go to the folder and find the
SqlWb.exe application. What's the result? Do you get any error message?
Please provide the entire error so that we may do the further troubleshoot.
Basically, we do not recommand move the SQL Management Studio folder and
the Visual Studio 2005 folder directly. This may cause some application
could not found the referenced files. The best way to move these folder is
re-install the Visual Studio and the SQL Management Studio.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei Lu,
I am referencing the folders that SS2K5 makes in the "My Documents" and
where can I change the pointer to another directory.
C:\Documents and Settings\sck10\My Documents\SQL Server Management Studio
Backup
Code Snippets
Projects
Settings
Templates
Thanks,
sck10
"Wei Lu" <weilu@.online.microsoft.com> wrote in message
news:nSxQTvBaGHA.880@.TK2MSFTNGXA01.phx.gbl...
> Hi sck,
> Thanks for using MSDN Managed Newsgroup Support.
> By default, the SQL Management Studio is located at %Program Files
> %\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE
\SqlWb.exe. If you
> moved the SQL Management Studio, please go to the folder and find the
> SqlWb.exe application. What's the result? Do you get any error message?
> Please provide the entire error so that we may do the further
troubleshoot.
> Basically, we do not recommand move the SQL Management Studio folder and
> the Visual Studio 2005 folder directly. This may cause some application
> could not found the referenced files. The best way to move these folder is
> re-install the Visual Studio and the SQL Management Studio.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ========================================
==========
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
==========
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>|||Hi sck10,
Thanks for the update.
My understanding of your issue is: You want to specify the location when
you create a project/ solution in SQL Management Studio. If I misunderstood
your concern, please feel free to let me know.
You could change the location where your Project store in the location
textbox. Also you can Browse to the location you want to store the project.
By default, SQL Management Studio will create the project in the My
Documents\SQL Server Management Studio\Projects folder.
Hope this will be helpful.
Sincerely,
Wei Lu
Microsoft Online Community Support
========================================
==========
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
==========
This posting is provided "AS IS" with no warranties, and confers no rights.
--
>From: "sck10" <sck10@.online.nospam>
>References: <#fQKPj6ZGHA.4116@.TK2MSFTNGP05.phx.gbl>
<nSxQTvBaGHA.880@.TK2MSFTNGXA01.phx.gbl>
>Subject: Re: Move SQL Server Management Studio Startup folder
>Date: Wed, 26 Apr 2006 08:52:15 -0500
>Lines: 49
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1807
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1807
>Message-ID: <eGEohiTaGHA.1240@.TK2MSFTNGP03.phx.gbl>
>Newsgroups: microsoft.public.sqlserver.server
>NNTP-Posting-Host: 11.202.185.135.in-addr.arpa 135.185.202.11
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.sqlserver.server:429301
>X-Tomcat-NG: microsoft.public.sqlserver.server
>Hi Wei Lu,
>I am referencing the folders that SS2K5 makes in the "My Documents" and
>where can I change the pointer to another directory.
>C:\Documents and Settings\sck10\My Documents\SQL Server Management Studio
>Backup
>Code Snippets
>Projects
>Settings
>Templates
>Thanks,
>sck10
>"Wei Lu" <weilu@.online.microsoft.com> wrote in message
>news:nSxQTvBaGHA.880@.TK2MSFTNGXA01.phx.gbl...
you[vbcol=seagreen]
>troubleshoot.
is[vbcol=seagreen]
>rights.
>
>|||I have the same problem. Allow me to restate the issue from my point of
view, and maybe someone has an answer:
When I am in Management Studio and choose File... Open... File, the
standard Open File dialog box lists 3 icons in the left side: Desktop, My
Projects, and My Computer. The My Projects folder points to My Documents/SQ
L
Server Management Studio/My Projects.
I understand that this is the default location. I would like to CHANGE the
default location to a different folder.
There doesn't seem to be an option to set this default location in the
Management Studio Options. I tried to find the reference in the registry,
but cannot.
Alternatively, I would be happy to be able to ADD my preferred folder to
this dialog

Saturday, February 25, 2012

move databases

Hi,
I like to move sql 2000 databases from 2003 server A, on drive D to 2003
server B on drive N. But master database would stop working after I moved to
server B, on drive N.
What I need to do to resolve the problem or is this do able?
Thanks
Check out:
http://support.microsoft.com/default.aspx/kb/224071
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
..
"anoni" <anoni@.discussions.microsoft.com> wrote in message
news:0B68D43F-A774-46F1-BE55-3D78D87D63FD@.microsoft.com...
Hi,
I like to move sql 2000 databases from 2003 server A, on drive D to 2003
server B on drive N. But master database would stop working after I moved to
server B, on drive N.
What I need to do to resolve the problem or is this do able?
Thanks

move databases

Hi,
I like to move sql 2000 databases from 2003 server A, on drive D to 2003
server B on drive N. But master database would stop working after I moved to
server B, on drive N.
What I need to do to resolve the problem or is this do able?
ThanksCheck out:
http://support.microsoft.com/default.aspx/kb/224071
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinpub.com
.
"anoni" <anoni@.discussions.microsoft.com> wrote in message
news:0B68D43F-A774-46F1-BE55-3D78D87D63FD@.microsoft.com...
Hi,
I like to move sql 2000 databases from 2003 server A, on drive D to 2003
server B on drive N. But master database would stop working after I moved to
server B, on drive N.
What I need to do to resolve the problem or is this do able?
Thanks