Summary Table
Categories |
Total Count |
PII |
1 |
URL |
0 |
DNS |
0 |
EKL |
0 |
IP |
0 |
PORT |
0 |
VsID |
0 |
CF |
0 |
AI |
0 |
VPD |
0 |
PL |
0 |
Other |
0 |
File Content
Before opening the solution, rename the solution to something more desirable with these steps. To provide a mental anchor, let's call the new project MyDbProject.
1. Rename Staging-Db.sln to MyDbProject.sln
2. Right-click on the MyDbProject.sln file and open in an editor (e.g., Notepad)
3. Replace any reference to Staging-Db with MyDbProject
4. Save the file
5. Rename the Staging-Db folder to MyDbProject
6. Drill down to the MyDbProject folder
7. Rename the Staging-Db.dbmdl file to MyDbProject.dbml
8. Rename the Staging-Db.sqlproj file to MyDbProject.sqlproj
9. Right-click on the MyDbProject.sqlproj file and open in an editor (e.g., Notepad)
10. Replace any reference to Staging_Db and Staging-Db with MyDbProject
11. Save the file
12. Rename the Staging-Db.sqlproj.user file to MyDbProject.sqlproj.user
13. The project is now safe to launch by double-clicking on the MyProject.sln file in the root folder.
If there are any errors in opening, then something in one of the files missed the renaming.
Any other troubles, please contact Ken
PII
)
The folder structure of the project is designed to be similar to that of SQL Server.
Plus the folders are the ones typically needed though not all-inclusive.
In addition, there are some files of interest to be aware of:
* Storage--Filegroups and Files--contains the typical filegroup/file structure that would be needed.
Some additional filegroups/files may be needed, depending on the nature of the data to be stored
* Programmability--Stored Procedures--contains to reporting stored procedures (uspRptWebLogDetails and uspRptGetDataDictionary)
* Programmability--Functions--contains two table-based user defined functions (ufnGetErrorInfo and ufnSplit)
* Security--Schemas--contains a zraw schema that is useful if there is a need to regularly bring in raw data from another source
and want to segregate those table objects from the ones located in dbo
* Security--Roles--contains a db_execute role. Creating this role and assigning Execute privileges to it makes it easier
to grant read/write/execute privileges to database back-end users and to web accounts, without an inordinate amount of
database object management (the alternative is ugly and time-consuming!)
* Tables--WebLogs is a sample table construct to make help facility table/constraints/indexes/data dictionary object creation;
includes comment marks for where to place things
TEST-