nomad
If I understood you correctly
1) Open Solution within you have added .sql files (1-for SP,2-for Views)
2) When you click on the file it opens a object explorer windows
3) Add your object to opened window (relevant for object type) and save it.
So , the next time you open the file your script should be saved there
"nomad" <d.bedgood@.ntlworld.com> wrote in message
news:1172065721.265467.175850@.a75g2000cwd.googlegr oups.com...
> Hi,
> I want to be able to use source control from within SQL 2005. I know
> how to add a new solution with a project attached. And I know how to
> add existing .sql scripts to it. My quesiton is, how can I split them
> up so that I can add all stored procedure scripts into a folder called
> Stored Procedures, all views into a folder called Views etc instead of
> them all going into the Query folder.
> Appreciate any help on this.
>
Ahh, I see what you mean. I'm affraid you cannot do that
"nomad" <d.bedgood@.ntlworld.com> wrote in message
news:1172068385.736309.197940@.k78g2000cwa.googlegr oups.com...
> On 21 Feb, 14:16, "Uri Dimant" <u...@.iscar.co.il> wrote:
> I know how to do all of this. My question is, in the solution you
> have folders called Connections, Queries & Miscellaneous. I want to
> be able to add folders called Stored Procedures, Views etc so that I
> can add my SP .sql scripts into Stored Procedure folder, Views scripts
> into Views folder etc so that it is easier to differentiate between
> your scripts.
>
Showing posts with label files. Show all posts
Showing posts with label files. Show all posts
Wednesday, March 28, 2012
Monday, March 26, 2012
help with server replacement
i'm replacing a server in the next few weeks.
the old server has all database files, log files, and error files on
f:\sql which is a drive on a san.
sql2000 program files are on c: and d:.
the new server will have the same name and same IP as the old server.
the only difference is new one is win2003 and old one is win2000.
i'm wondering if this will work.
create disk partition on new server f:
install sql2000 program files on c: and d:.
install sql2000 data, log, and error files in f:\sql
shut down sql2000.
delete f:
shut down old server.
connect new server to network.
attach the san drive to new server as f: (has all the databases from old
server).
start sql server.
think that will work?
or will i have to install master, model, msdb, tempdb on e: and then
detach the ones on e: and then attach the ones on f:?
last time i did that, it was a nightmare. i couldn't get sql server to
start for like an hour because the kb article had faulty instructions.Hi,
There are several factors you need to consider. I suggest you go through
these articles, list down each of the activities (something like checklist)
and execute it.
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://www.support.microsoft.com/?id=314546
INF: Using the WITH MOVE Option with the RESTORE Statement
http://support.microsoft.com/?id=221465
PRB: User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=246133
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://www.support.microsoft.com/?id=274188
How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers
http://www.support.microsoft.com/?id=240872
SAMPLE: Mapsids.exe Helps Map SIDs Between User and Master Databases When
Database Is Moved
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
Thanks
GYKsql
the old server has all database files, log files, and error files on
f:\sql which is a drive on a san.
sql2000 program files are on c: and d:.
the new server will have the same name and same IP as the old server.
the only difference is new one is win2003 and old one is win2000.
i'm wondering if this will work.
create disk partition on new server f:
install sql2000 program files on c: and d:.
install sql2000 data, log, and error files in f:\sql
shut down sql2000.
delete f:
shut down old server.
connect new server to network.
attach the san drive to new server as f: (has all the databases from old
server).
start sql server.
think that will work?
or will i have to install master, model, msdb, tempdb on e: and then
detach the ones on e: and then attach the ones on f:?
last time i did that, it was a nightmare. i couldn't get sql server to
start for like an hour because the kb article had faulty instructions.Hi,
There are several factors you need to consider. I suggest you go through
these articles, list down each of the activities (something like checklist)
and execute it.
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://www.support.microsoft.com/?id=314546
INF: Using the WITH MOVE Option with the RESTORE Statement
http://support.microsoft.com/?id=221465
PRB: User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=246133
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://www.support.microsoft.com/?id=274188
How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers
http://www.support.microsoft.com/?id=240872
SAMPLE: Mapsids.exe Helps Map SIDs Between User and Master Databases When
Database Is Moved
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
Thanks
GYKsql
help with server replacement
i'm replacing a server in the next few weeks.
the old server has all database files, log files, and error files on
f:\sql which is a drive on a san.
sql2000 program files are on c: and d:.
the new server will have the same name and same IP as the old server.
the only difference is new one is win2003 and old one is win2000.
i'm wondering if this will work.
create disk partition on new server f:
install sql2000 program files on c: and d:.
install sql2000 data, log, and error files in f:\sql
shut down sql2000.
delete f:
shut down old server.
connect new server to network.
attach the san drive to new server as f: (has all the databases from old
server).
start sql server.
think that will work?
or will i have to install master, model, msdb, tempdb on e: and then
detach the ones on e: and then attach the ones on f:?
last time i did that, it was a nightmare. i couldn't get sql server to
start for like an hour because the kb article had faulty instructions.
Hi,
There are several factors you need to consider. I suggest you go through
these articles, list down each of the activities (something like checklist)
and execute it.
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://www.support.microsoft.com/?id=314546
INF: Using the WITH MOVE Option with the RESTORE Statement
http://support.microsoft.com/?id=221465
PRB: User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=246133
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://www.support.microsoft.com/?id=274188
How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers
http://www.support.microsoft.com/?id=240872
SAMPLE: Mapsids.exe Helps Map SIDs Between User and Master Databases When
Database Is Moved
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
Thanks
GYK
the old server has all database files, log files, and error files on
f:\sql which is a drive on a san.
sql2000 program files are on c: and d:.
the new server will have the same name and same IP as the old server.
the only difference is new one is win2003 and old one is win2000.
i'm wondering if this will work.
create disk partition on new server f:
install sql2000 program files on c: and d:.
install sql2000 data, log, and error files in f:\sql
shut down sql2000.
delete f:
shut down old server.
connect new server to network.
attach the san drive to new server as f: (has all the databases from old
server).
start sql server.
think that will work?
or will i have to install master, model, msdb, tempdb on e: and then
detach the ones on e: and then attach the ones on f:?
last time i did that, it was a nightmare. i couldn't get sql server to
start for like an hour because the kb article had faulty instructions.
Hi,
There are several factors you need to consider. I suggest you go through
these articles, list down each of the activities (something like checklist)
and execute it.
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://www.support.microsoft.com/?id=314546
INF: Using the WITH MOVE Option with the RESTORE Statement
http://support.microsoft.com/?id=221465
PRB: User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=246133
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://www.support.microsoft.com/?id=274188
How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers
http://www.support.microsoft.com/?id=240872
SAMPLE: Mapsids.exe Helps Map SIDs Between User and Master Databases When
Database Is Moved
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
Thanks
GYK
help with server replacement
i'm replacing a server in the next few weeks.
the old server has all database files, log files, and error files on
f:\sql which is a drive on a san.
sql2000 program files are on c: and d:.
the new server will have the same name and same IP as the old server.
the only difference is new one is win2003 and old one is win2000.
i'm wondering if this will work.
create disk partition on new server f:
install sql2000 program files on c: and d:.
install sql2000 data, log, and error files in f:\sql
shut down sql2000.
delete f:
shut down old server.
connect new server to network.
attach the san drive to new server as f: (has all the databases from old
server).
start sql server.
think that will work?
or will i have to install master, model, msdb, tempdb on e: and then
detach the ones on e: and then attach the ones on f:?
last time i did that, it was a nightmare. i couldn't get sql server to
start for like an hour because the kb article had faulty instructions.Hi,
There are several factors you need to consider. I suggest you go through
these articles, list down each of the activities (something like checklist)
and execute it.
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://www.support.microsoft.com/?id=314546
INF: Using the WITH MOVE Option with the RESTORE Statement
http://support.microsoft.com/?id=221465
PRB: User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=246133
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://www.support.microsoft.com/?id=274188
How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers
http://www.support.microsoft.com/?id=240872
SAMPLE: Mapsids.exe Helps Map SIDs Between User and Master Databases When
Database Is Moved
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
--
Thanks
GYK
the old server has all database files, log files, and error files on
f:\sql which is a drive on a san.
sql2000 program files are on c: and d:.
the new server will have the same name and same IP as the old server.
the only difference is new one is win2003 and old one is win2000.
i'm wondering if this will work.
create disk partition on new server f:
install sql2000 program files on c: and d:.
install sql2000 data, log, and error files in f:\sql
shut down sql2000.
delete f:
shut down old server.
connect new server to network.
attach the san drive to new server as f: (has all the databases from old
server).
start sql server.
think that will work?
or will i have to install master, model, msdb, tempdb on e: and then
detach the ones on e: and then attach the ones on f:?
last time i did that, it was a nightmare. i couldn't get sql server to
start for like an hour because the kb article had faulty instructions.Hi,
There are several factors you need to consider. I suggest you go through
these articles, list down each of the activities (something like checklist)
and execute it.
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://www.support.microsoft.com/?id=314546
INF: Using the WITH MOVE Option with the RESTORE Statement
http://support.microsoft.com/?id=221465
PRB: User Logon and/or Permission Errors After Restoring Dump
http://www.support.microsoft.com/?id=168001
HOW TO: Transfer Logins and Passwords Between Instances of SQL Server
http://www.support.microsoft.com/?id=246133
PRB: "Troubleshooting Orphaned Users" Topic in Books Online is Incomplete
http://www.support.microsoft.com/?id=274188
How to Resolve Permission Issues When a Database Is Moved Between SQL
Servers
http://www.support.microsoft.com/?id=240872
SAMPLE: Mapsids.exe Helps Map SIDs Between User and Master Databases When
Database Is Moved
http://www.support.microsoft.com/?id=298897
Utility to map users to the correct login
http://www.dbmaint.com/SyncSqlLogins.asp
--
Thanks
GYK
Monday, February 27, 2012
Help with moving database from SQL 7 to SQL 2000
Hello. I'm having problems moving a database from SQL 7 to SQL 2000. The way
I did it was copy the .mdf and .ldf files over to SQL 2000. Both SQL servers
are using different computer names. But I'm missing some views, stored
procedures, jobs, and user accounts. I'm assuming this must be the wrong way
to do it.
Could you someone recommend what is the proper way to move the database over
from SQL 7 to SQL 2000 while maintaining all the data?
Thanks in advance!
Please check this article:
http://support.microsoft.com/default...en-us;314546#2
It contain detail information on how to move DBs, logins, etc.
Regards.
"SQL Newbie" wrote:
> Hello. I'm having problems moving a database from SQL 7 to SQL 2000. The way
> I did it was copy the .mdf and .ldf files over to SQL 2000. Both SQL servers
> are using different computer names. But I'm missing some views, stored
> procedures, jobs, and user accounts. I'm assuming this must be the wrong way
> to do it.
> Could you someone recommend what is the proper way to move the database over
> from SQL 7 to SQL 2000 while maintaining all the data?
> Thanks in advance!
I did it was copy the .mdf and .ldf files over to SQL 2000. Both SQL servers
are using different computer names. But I'm missing some views, stored
procedures, jobs, and user accounts. I'm assuming this must be the wrong way
to do it.
Could you someone recommend what is the proper way to move the database over
from SQL 7 to SQL 2000 while maintaining all the data?
Thanks in advance!
Please check this article:
http://support.microsoft.com/default...en-us;314546#2
It contain detail information on how to move DBs, logins, etc.
Regards.
"SQL Newbie" wrote:
> Hello. I'm having problems moving a database from SQL 7 to SQL 2000. The way
> I did it was copy the .mdf and .ldf files over to SQL 2000. Both SQL servers
> are using different computer names. But I'm missing some views, stored
> procedures, jobs, and user accounts. I'm assuming this must be the wrong way
> to do it.
> Could you someone recommend what is the proper way to move the database over
> from SQL 7 to SQL 2000 while maintaining all the data?
> Thanks in advance!
Help with moving database from SQL 7 to SQL 2000
Hello. I'm having problems moving a database from SQL 7 to SQL 2000. The way
I did it was copy the .mdf and .ldf files over to SQL 2000. Both SQL servers
are using different computer names. But I'm missing some views, stored
procedures, jobs, and user accounts. I'm assuming this must be the wrong way
to do it.
Could you someone recommend what is the proper way to move the database over
from SQL 7 to SQL 2000 while maintaining all the data?
Thanks in advance!Please check this article:
http://support.microsoft.com/defaul...;en-us;314546#2
It contain detail information on how to move DBs, logins, etc.
Regards.
"SQL Newbie" wrote:
> Hello. I'm having problems moving a database from SQL 7 to SQL 2000. The w
ay
> I did it was copy the .mdf and .ldf files over to SQL 2000. Both SQL serve
rs
> are using different computer names. But I'm missing some views, stored
> procedures, jobs, and user accounts. I'm assuming this must be the wrong w
ay
> to do it.
> Could you someone recommend what is the proper way to move the database ov
er
> from SQL 7 to SQL 2000 while maintaining all the data?
> Thanks in advance!
I did it was copy the .mdf and .ldf files over to SQL 2000. Both SQL servers
are using different computer names. But I'm missing some views, stored
procedures, jobs, and user accounts. I'm assuming this must be the wrong way
to do it.
Could you someone recommend what is the proper way to move the database over
from SQL 7 to SQL 2000 while maintaining all the data?
Thanks in advance!Please check this article:
http://support.microsoft.com/defaul...;en-us;314546#2
It contain detail information on how to move DBs, logins, etc.
Regards.
"SQL Newbie" wrote:
> Hello. I'm having problems moving a database from SQL 7 to SQL 2000. The w
ay
> I did it was copy the .mdf and .ldf files over to SQL 2000. Both SQL serve
rs
> are using different computer names. But I'm missing some views, stored
> procedures, jobs, and user accounts. I'm assuming this must be the wrong w
ay
> to do it.
> Could you someone recommend what is the proper way to move the database ov
er
> from SQL 7 to SQL 2000 while maintaining all the data?
> Thanks in advance!
Help with moving database from SQL 7 to SQL 2000
Hello. I'm having problems moving a database from SQL 7 to SQL 2000. The way
I did it was copy the .mdf and .ldf files over to SQL 2000. Both SQL servers
are using different computer names. But I'm missing some views, stored
procedures, jobs, and user accounts. I'm assuming this must be the wrong way
to do it.
Could you someone recommend what is the proper way to move the database over
from SQL 7 to SQL 2000 while maintaining all the data?
Thanks in advance!Please check this article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;314546#2
It contain detail information on how to move DBs, logins, etc.
Regards.
"SQL Newbie" wrote:
> Hello. I'm having problems moving a database from SQL 7 to SQL 2000. The way
> I did it was copy the .mdf and .ldf files over to SQL 2000. Both SQL servers
> are using different computer names. But I'm missing some views, stored
> procedures, jobs, and user accounts. I'm assuming this must be the wrong way
> to do it.
> Could you someone recommend what is the proper way to move the database over
> from SQL 7 to SQL 2000 while maintaining all the data?
> Thanks in advance!
I did it was copy the .mdf and .ldf files over to SQL 2000. Both SQL servers
are using different computer names. But I'm missing some views, stored
procedures, jobs, and user accounts. I'm assuming this must be the wrong way
to do it.
Could you someone recommend what is the proper way to move the database over
from SQL 7 to SQL 2000 while maintaining all the data?
Thanks in advance!Please check this article:
http://support.microsoft.com/default.aspx?scid=kb;en-us;314546#2
It contain detail information on how to move DBs, logins, etc.
Regards.
"SQL Newbie" wrote:
> Hello. I'm having problems moving a database from SQL 7 to SQL 2000. The way
> I did it was copy the .mdf and .ldf files over to SQL 2000. Both SQL servers
> are using different computer names. But I'm missing some views, stored
> procedures, jobs, and user accounts. I'm assuming this must be the wrong way
> to do it.
> Could you someone recommend what is the proper way to move the database over
> from SQL 7 to SQL 2000 while maintaining all the data?
> Thanks in advance!
Sunday, February 19, 2012
help with large log files
Xref: TK2MSFTNGP08.phx.gbl microsoft.public.sqlserver.clients:30825
Hi,
In SQL Server Enterprise Manager > Space Allocation. I can not reduce the
current size. I can restrict the to current size but I can not reduce it.
This lay person very much appreciates your help.
regards
S
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.805 / Virus Database: 547 - Release Date: 03-Dec-04
Have alook at these:
http://www.nigelrivett.net/Transacti...leGrows_1.html Log File issues
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
http://www.support.microsoft.com/?id=256650 INF: How to Shrink the SQL
Server 7.0 Tran Log
http://www.support.microsoft.com/?id=272318 INF: Shrinking Log in SQL
Server 2000 with DBCC SHRINKFILE
http://www.karaszi.com/SQLServer/info_dont_shrink.asp Shrinking
considerations
Andrew J. Kelly SQL MVP
"Neither rhyme nor reason" <sportman_6663@.yahoo.ca> wrote in message
news:4Fl0e.8116$JK1.566630@.news20.bellglobal.com.. .
> Hi,
> In SQL Server Enterprise Manager > Space Allocation. I can not reduce the
> current size. I can restrict the to current size but I can not reduce it.
> This lay person very much appreciates your help.
>
> regards
> S
>
> --
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.805 / Virus Database: 547 - Release Date: 03-Dec-04
>
Hi,
In SQL Server Enterprise Manager > Space Allocation. I can not reduce the
current size. I can restrict the to current size but I can not reduce it.
This lay person very much appreciates your help.
regards
S
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.805 / Virus Database: 547 - Release Date: 03-Dec-04
Have alook at these:
http://www.nigelrivett.net/Transacti...leGrows_1.html Log File issues
http://www.support.microsoft.com/?id=317375 Log File Grows too big
http://www.support.microsoft.com/?id=110139 Log file filling up
http://www.mssqlserver.com/faq/logs-shrinklog.asp Shrink File
http://www.support.microsoft.com/?id=315512 Considerations for Autogrow
and AutoShrink
http://www.support.microsoft.com/?id=256650 INF: How to Shrink the SQL
Server 7.0 Tran Log
http://www.support.microsoft.com/?id=272318 INF: Shrinking Log in SQL
Server 2000 with DBCC SHRINKFILE
http://www.karaszi.com/SQLServer/info_dont_shrink.asp Shrinking
considerations
Andrew J. Kelly SQL MVP
"Neither rhyme nor reason" <sportman_6663@.yahoo.ca> wrote in message
news:4Fl0e.8116$JK1.566630@.news20.bellglobal.com.. .
> Hi,
> In SQL Server Enterprise Manager > Space Allocation. I can not reduce the
> current size. I can restrict the to current size but I can not reduce it.
> This lay person very much appreciates your help.
>
> regards
> S
>
> --
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.805 / Virus Database: 547 - Release Date: 03-Dec-04
>
Subscribe to:
Posts (Atom)